You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've noticed the performance of the Ruby driver and Mongoid's test suites decreasing with JRuby versions following 1.7 and am looking for ideas on how to investigate.
The Ruby driver's test suite on travis can be seen here.
The test suite runs in 1 - 2 minutes on MRI (performance is not hugely different between MRI versions)
JRuby 1.7: takes from 3 - 4 minutes
JRuby 9.1.2.0: it takes from 7 - 10 minutes
Mongoid's test suite shows the same trend but uses a lot of memory on JRuby 9.1.2.0. I have a branch for testing Mongoid on JRuby and comparing the performance to MRI here
I've set the jruby-openssl gem version to 0.9.17 on that branch, so this issue doesn't seem to be the culprit.
The branch has the JRUBY_OPTS Xmx-- setting at 1G
While I can continue to increase the limit until the process doesn't run out of memory, the performance is surprising. I've done some profiling on some of the most common Model methods in Mongoid but haven't found any valuable information yet.
I'd welcome any ideas you might have, thanks!
The text was updated successfully, but these errors were encountered:
I've noticed the performance of the Ruby driver and Mongoid's test suites decreasing with JRuby versions following 1.7 and am looking for ideas on how to investigate.
The Ruby driver's test suite on travis can be seen here.
Mongoid's test suite shows the same trend but uses a lot of memory on JRuby 9.1.2.0. I have a branch for testing Mongoid on JRuby and comparing the performance to MRI here
Xmx--
setting at 1GWhile I can continue to increase the limit until the process doesn't run out of memory, the performance is surprising. I've done some profiling on some of the most common Model methods in Mongoid but haven't found any valuable information yet.
I'd welcome any ideas you might have, thanks!
The text was updated successfully, but these errors were encountered: