On Mon, Sep 10, 2012 at 11:27 PM, Robert K.
On Mon, Sep 10, 2012 at 10:16 PM, jason marshall [email protected]
We have a Rails app running on Ruby 1.9.3, and a under Windows we’re
a 20x time penalty in our RSpec tests.
And the hardware is comparable?
Yes, good question. On the same model hardware, it’s 20x initial, 4.5x
current. (2000, 440, vs <100 seconds)
I’m fairly new to Ruby, but not to performance analysis, so I’ve
to follow up on this problem. If I want to file/find a bug to associate
with this problem, what sort of data should I be gathering, and how?
I have zero experience with Rails profiling, but maybe using the std
lib profiler can give you a first data point.
Yeah my readings from Google say it’s not easy to do what I need to do.
I’m hoping someone could talk me down from the ledge and point me to a
times longer to run. Dots just accumulate slower.
Just to exclude an obvious issue: do you have an AV engine up and
running on the Windows box? If yes, excluding some directories might
help. Some engines then still slow down operation so completely
switching off for the test might also be an option to determine
whether it’s AV.
I’ll entertain the question, but let’s take it as a given that turning
AV on Windows is a very, very unwise action.
Those numbers reflect my project directory already being excluded. I’m
sure I’m comfortable having Ruby whitelisted, though it’s an interesting
With Ruby exclusion, Regular is 1490 seconds, patched is 400 seconds.
To exclude something else: is there concurrent activity that eats CPU
and / or IO bandwidth?
Not much. Or at least, there’s not a lot of jitter in the numbers. I
have RubyMine and a web browser (low CPU) open.
remember.guy do |as, often| as.you_can - without end
As a mostly unrelated anecdote, the Subversion team had conversations
this for a long time, and resisted making changes for a number of years.
In the 1.7 release they made some pretty substantial changes to how
use the filesystem, and ended up with something that was both simpler
users) and happened to work a hell of a lot faster on Windows.
It sounds like you guys are on that path at least.