[JAVA-203] get different throughput when using db.slaveOk() versus db.collection.addOption(Bytes.QUERYOPTION_SLAVEOK) Created: 26/Oct/10 Updated: 29/Oct/10 Resolved: 27/Oct/10 |
|
| Status: | Closed |
| Project: | Java Driver |
| Component/s: | Performance |
| Affects Version/s: | 2.2 |
| Fix Version/s: | 2.3 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Alvin Richards (Inactive) | Assignee: | Eliot Horowitz (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
EC2 / Ubuntu 10.04 |
||
| Attachments: |
|
| Description |
|
Problem: Case 1: db.slaveOk() Case 2: db.collection.addOption(Bytes.QUERYOPTION_SLAVEOK) Workaround: Reproduce:
Business Case:
|
| Comments |
| Comment by Eliot Horowitz (Inactive) [ 27/Oct/10 ] |
|
changed count() to make it more intuitive |
| Comment by auto [ 27/Oct/10 ] |
|
Author: {'login': 'erh', 'name': 'Eliot Horowitz', 'email': 'eliot@10gen.com'}Message: count follows collection options |
| Comment by Eliot Horowitz (Inactive) [ 27/Oct/10 ] |
|
No - i actually made sure to query things so the sub system was initialized |
| Comment by Eliot Horowitz (Inactive) [ 27/Oct/10 ] |
|
with 5% for me after modifying test to initialize slave connections before starting timer |
| Comment by Alvin Richards (Inactive) [ 27/Oct/10 ] |
|
Actually, looking at the results there is a 4x perf drop using db.slaveOk() versus collection.addOption(Bytes.QUERYOPTION_SLAVEOK). |
| Comment by Alvin Richards (Inactive) [ 27/Oct/10 ] |
|
Appears to be resolved with the master $ java -cp mongo.jar:./bin com.test.SlaveTest "10.196.130.32:27000,10.203.61.5:27000" test blogs 1 3 $ java -cp mongo.jar:./bin com.test.SlaveTest "10.196.130.32:27000,10.203.61.5:27000" test blogs 2 3 |
| Comment by Eliot Horowitz (Inactive) [ 27/Oct/10 ] |
|
Did you try master? |