3 ms·
This is a good point that I didn't consider. Running the 'just iterate over the range version' of this code with jruby: [master] clifff@fair_and_square: ru
by ClifReeder 13y ago
This is a good point that I didn't consider. Running the 'just iterate over the range version' of this code with jruby:
[master] clifff@fair_and_square: ruby -v
jruby 1.7.3 (1.9.3p385) 2013-02-21 dac429b on Java HotSpot(TM) 64-Bit Server VM 1.6.0_43-b01-447-11M4203 [darwin-x86_64]
[master] clifff@fair_and_square: time ruby fair_and_square.rb C-large-1.in.bak
real 6m39.105s
user 6m37.762s
sys 0m19.009s
- aghoreyshi 13y agoWhat is sys time? The amount of time it's actually run on the processor?
- eatitraw 13y agoNo, it is the amount of time your program spent in system calls: http://stackoverflow.com/questions/556405/what-do-real-user-and-sys-mean-in-the-output-of-time1 http://stackoverflow.com/questions/556405/what-do-real-user-...
- jmah 13y agoThe amount of time spent in system calls (i.e. the kernel).
- digger250 13y agoWhen I run the benchmark in C-ruby (2.0.0) I get: real 2m35.450s user 2m35.257s sys 0m0.139s On jruby with invokedynamic: time ruby -Xcompile.invokedynamic=true file2.rb C-large-1.in real 1m17.711s user 1m15.618s sys 0m0.830s In jruby without invokedynamic time ruby file2.rb C-large-1.in real 1m37.856s user 1m39.260s sys 0m0.854s