|
1. Has Xindice at this time any kind of
built-in locking mechanisms, i.e. if more writes to the DB occur, does it
handle them well ? Or should the programmer take care of the
delails?
2. I ran some benchmarks (ab = Apache
Benchmark) on 2 servlets which access Xindice via XML:DB and respectively
XMLRPC (and performs a query like "//*count(*)=2")
Both of them gave very poor results, but XMLRPC was
(surprisingly) faster.
Anyhow, with 100 requests of which 10 concurrent,
the failed request percent was like 70-80% !
Even with 2 concurrent requests the failed rate was
20-30%.
I suspect a concurrency problem with Xindice if not
with Tomcat....
After the tests, the system ran more then 1000 java
processes (both tomcat and xindice, apparently)
which did noy die until I killed them.
Test system:
Siemens PIII 500MHz
192MB SDRAMRAM PC100
HDD w/UDMA
RedHAt Linux 7.0
Xindice 1.0
Tomcat 4.0.3
Thanks for any comments.
Florin Tudor
Web Application Developer /
Consultant
Middleware & Programming Dept. Integrator /SAP Romania www.sap.ro, www.integrare.ro |
