Created
December 13, 2013 10:01
-
-
Save coffeemug/7942219 to your computer and use it in GitHub Desktop.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| David, sorry you ran into these issues. The crash is a known bug, and will be fixed in the 1.12 release (along with the new cache implementation). See https://github.com/rethinkdb/rethinkdb/issues/1389 for more details. | |
| As to the performance you're getting, could you give some additional info so we could track this down? | |
| - Which OS/version are you running? | |
| - Which RethinkDB version are you running? (you can tell by running `rethinkdb --version`) | |
| - Which client driver are you using (and which version)? | |
| - What query do you use to get out 100 documents and how are you measuing latency? | |
| Would really appreciate your feedback so we could fix these issues. |
@jdoliner yeah check the vmstat I posted above. It's all cpu.
@wildattire -- thank you for submitting the detailed report, it helps immensely. Let's keep track of this in rethinkdb/rethinkdb#1766. We'll try to get to this as soon as we can.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The event "Do range scan on primary index" includes the time needed to read the values off of disk. Do you know if any IO does happen while the query is being performed? Or is all of the data in memory?