-
Type: Improvement
-
Resolution: Done
-
Priority: Major - P3
-
None
-
Affects Version/s: 2.3
-
Component/s: Performance
-
None
-
Environment:Ubuntu 10.04 x64, mongodb-unstable 20101028, mongo-java-driver 2.3, quadcore, 3.2G RAM
when running my testcase (attachment)
i get these values back:
======================================================================================== Testname: 1 Thread # of Threads: 1 # of Loops: 400 # of values: 400 Average Returned Values: 100 Average Time: 53ms ======================================================================================== ======================================================================================== Testname: 5 Thread # of Threads: 5 # of Loops: 800 # of values: 4000 Average Returned Values: 100 Average Time: 196ms ======================================================================================== ======================================================================================== Testname: 10 Thread # of Threads: 10 # of Loops: 40 # of values: 400 Average Returned Values: 100 Average Time: 458ms ======================================================================================== ======================================================================================== Testname: 20 Thread # of Threads: 20 # of Loops: 20 # of values: 400 Average Returned Values: 100 Average Time: 1020ms ========================================================================================
so 20 threads use approx 988ms per query,
one thread uses approx 53ms, so 20 concurrent requests seem to increase the query time by factor 20 ...
is this to be expected? is this a known issue? can we tweak it somewhere?
- depends on
-
JAVA-221 Try to remove synchronized in DBApiLayer finalize
- Closed