> Hi all
>
> We are currently considering using Slide for some project, and have done
> some preliminary analysis and tests on it. The only thing really
> stopping us is the surprisingly poor performance results we got during
> the tests. You can find the test report along with the source code to
> the test tool and domain files here:
> http://www.team-vision.com.mk/ivan/slide
>
> Slide performance when dealing with objects of size 2-4 KB is on the
> order of 20 to 70 of kilobytes per second! The tests were done with MS
> SQL Server and Oracle as backends on a an idle 100 MBps LAN.
>
> There we're also some strange exceptions occuring, for instance Oracle's
> JDBC driver complained about having too many cursors open when the
> number of iterations was increased to 1000, and the JVM died with an
> OutOfMemoryError when the object size was increased (it was started with
> the -Xmx option specifying 512MB heap size), so there are concerns about
> serious resource leakage in Slide, especially after prolonged use.

Those cursors problems should have been addressed in a large part since
1.0.16. 1.0.17 should have many of those fixes.

Also, it is likely that using the JDBC content store is a lot slower than
the filesystem content store. It may also be unreliable with a lot of
databases (like hSQL). The most reasonable combination at the moment should
be JDBC descr store (or J2EE descr store if you're using the nightly builds)
+ filesystem content store, and it should have acceptable performance.

Remy


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to