I get reported execution total time from 84 to 102 seconds, while it
actually took not more than 25 seconds.
I set environment wariable RUBY_PROF_CPU_FREQUENCY to various values
scaling them 10 times, but it seemes had no influence on execution total
time. Also I tried same with --mode key values cpu, wall.
I set environment wariable RUBY_PROF_CPU_FREQUENCY to various values
scaling them 10 times, but it seemes had no influence on execution total
time. Also I tried same with --mode key values cpu, wall.
which version of ruby-prof? (RUBY_PROF_CPU_FREQUENCY only helps with
timing if you have an Intel chip and use that mode).
Thanks.
-r
Thanks for the kick in the pants to use rake compiler
Hi, Roger
updated gem and made two series of shots with the same two
RUBY_PROF_CPU_FREQUENCY values. Both RUBY_PROF_CPU_FREQUENCY values
178241142 and 1782411428 result in 18-19 secs
Now it reports more realistic - 18 secs while it took about 23 secs as
showed my watch. A compared my watch to computer clock, and found it’s
ok ) Could the difference take place due to concurrent process execution
environment?
Hi, Roger
updated gem and made two series of shots with the same two
RUBY_PROF_CPU_FREQUENCY values. Both RUBY_PROF_CPU_FREQUENCY values
178241142 and 1782411428 result in 18-19 secs
Now it reports more realistic - 18 secs while it took about 23 secs as
showed my watch. A compared my watch to computer clock, and found it’s
ok ) Could the difference take place due to concurrent process execution
environment?
Note well that it won’t actually use RUBY_PROF_CPU_FREQUENCY unless you
specify --mode=cpu
Thanks!
-rp
Roger,
I like ruby-prof, and find it very helpful. Thank you for it! And best
wishes )
Hi, Roger
updated gem and made two series of shots with the same two
RUBY_PROF_CPU_FREQUENCY values. Both RUBY_PROF_CPU_FREQUENCY values
178241142 and 1782411428 result in 18-19 secs
Now it reports more realistic - 18 secs while it took about 23 secs as
showed my watch. A compared my watch to computer clock, and found it’s
ok ) Could the difference take place due to concurrent process execution
environment?
Note well that it won’t actually use RUBY_PROF_CPU_FREQUENCY unless you
specify --mode=cpu
Thanks!
-rp
This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.