Paul; Please note the support Tiers we have defied for data back-ends in the Supported Repository Database Configurations section of http://www.topquadrant.com/products/supportedPlatforms3.6.html. We work closely with the Tier-1 data stores to ensure proper performance and feature sets. We will prioritize reports on these data back-ends that are failing to meet performance and other expectations of our customers. The other back-ends are supported on an as-is basis.
For Sesame/TBC, if you can give us specific parameters on when and how performance fails to meet expectations, we will prioritize the report for this fall when we do some maintenance work focusing on TBC. -- Scott On Jun 6, 12:41 am, PaulZH <p...@proxml.be> wrote: > Was too quick. > > I made first the ttl file within TBC, then exported it via TBC to the > remote sesame. > > Doing now a simple query from within TBC to the remote sesame takes > forever. > > The same query works fluently: > - in TBC on the original local ttl file > - in the Sesame workbench > - just HTTP posting it to the remote Sesame. > > Paul > > On May 31, 4:45 pm, PaulZH <p...@proxml.be> wrote: > > > > > > > > > Hi Holger, > > > > If you have time, an option worth trying would be to do the import of > > > the ttl file from TBC or SPARQLMotion, and not via Sesame directly. > > > If importing via TBC, the performance seems to be OK. > > > >The > > > difference would be that it will then use Jena bnode identifiers and > > > these may be easier to round-trip. > > > This seems to be the case. Will do further testing. > > > >Sorry we are a bit short on time with > > > SemTech preparations right now so may not be able to look into this > > > issue ourselves for a while. > > > Understood, no problem. > > However the client would like to keep, if possible, the initial > > workflow, so it would be nice if you could find some time to look at > > it when SemTech is over. > > > Paul -- You received this message because you are subscribed to the Google Group "TopBraid Suite Users", the topics of which include Enterprise Vocabulary Network (EVN), TopBraid Composer, TopBraid Live, TopBraid Ensemble, SPARQLMotion and SPIN. To post to this group, send email to topbraid-users@googlegroups.com To unsubscribe from this group, send email to topbraid-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/topbraid-users?hl=en
