Skip to Content.
Sympa Menu

perfsonar-dev - Re: [pS-dev] performance tests for lookup service

Subject: perfsonar development work

List archive

Re: [pS-dev] performance tests for lookup service


Chronological Thread 
  • From: Slawomir Trzaszczka <>
  • To: Michael Bischoff <>
  • Cc: Antoine Delvaux <>, "" <>, Maciej Glowiak <>
  • Subject: Re: [pS-dev] performance tests for lookup service
  • Date: Fri, 27 Nov 2009 09:17:38 +0100

On Thu, 2009-11-26 at 20:15 +0100, Michael Bischoff wrote:
> Hello all,
>
> The LS part of the perfSONAR protocol depends upon xquery and as far
> xml databases go the choices are limited.

Yes, I agree. There are 3,4 databases which uses xquery. Maybe someone
performed some tests for other databases and could say something more
about it ?

ExistDb has new release (1.4) . I think Exists' developers work very
hard on this product and maybe they improve much more performance of
this database. Exists' developers prepared some documentation about
performance tuning :

http://exist-db.org/tuning.html

I read it and tried to use this tips, but the result of this work didn't
enhance database so good (10 % increase of efficient).

Regards,

Slawek



> But considering the xquery
> part isn't used in all requests and those that due make up (rough
> estimate) <20% of the requests it might pay off to keep two data
> structures. One 'slower' that allows one to execute xqueries one that
> is for the bulk of the messages. I'm working on a prototype to see
> what this approach yields / could yield.
>
> With the above in mind is anyone prepared to collect statistics on the
> distribution of message types?
> Are the benchmarks avail / would you be prepared to run them again
> against the prototype
>
> kind regards,
>
> Michael
>
> Quoting Antoine Delvaux
> <>:
>
> > Hi Slawek,
> >
> > Indeed, interesting work and results. We can say that pSbase2 is
> > about 2 times more efficient than pSbase1, so we're already hoping
> > for pSbase10 ;-)
> >
> > I guess you performed those tests in a serial fashion: doing all
> > registrations, than all queries, then all deregistrations. Would
> > doing it in a more random fashion (registrations, queries and
> > deregistrations not happening all together), more similar to real
> > world usage, change the result pattern?
> >
> > You say the bottleneck is eXistDB, would it be possible to make a
> > prototype using some other DB engine like Postgresql to see if there
> > could be any other performance gain. Or does our code uses
> > advanced XML functions only provided by eXistDB?
> >
> > Beste regards,
> > --
> > Antoine Delvaux Systems Engineer
> > DANTE Skype: toninb
> > http://www.dante.net Tel: +221.778197275
> > PGP fingerprint: DC65 0D8B 6938 9229 33C3 18CA 4EB6 09D3 A333 3378
> >
> >
> >
> >
> >
>
>
--
+--------------------------------------------+
Slawomir Trzaszczka

Poznan Supercomputing & Networking Center
+--------------------------------------------+




Archive powered by MHonArc 2.6.16.

Top of Page