Hello, we're running a JAVA EE solution in an productive enviroment with sedna as database. We have about 10 simultanous users that work on 10 collections with about 10 Documents each (with 6 users in one collection). Lately we had strange performance issues with the database.
Sometimes sedna needs about 30-60 seconds for the easiest queries which normally are processed fast. It doesn't depend on the queries. I assume it has something todo with transaction conflicts. I went through the sedna documentation and found out that there was an update in Sedna 3.0 for the C API: SEDNA_ATTR_CONCURRENCY_TYPE was introduced to mark transactions as read-only, so that they don't conflict with other concurrent transactions. Unfortunatly there is no option in the Java Api to mark transactions as read only. I assume our problems have something to do with this, because these problems don't occur if we work with a single user in our development environment. Will there be an update for the Java Api in near future? We could use a wrapper instead ... Has anybody made benchmarks how -max-trs-num -upd-crt influence performance? Stefan ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ Sedna-discussion mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sedna-discussion
