On Sat, 08 Jul 2006, Charles O Nutter defenestrated me:
>
>I'm starting to run some profiles to find real hotspot problems. So
>here's the first summary of findings.
>Profiling: today's code, gem install --force rake (gem cached
>locally), up to some time during ri generation (kill
That's true; that would cut it down a little bit. Maybe I'll do a little analysis today on the C Ruby code to see when it actually handles thread context switches...perhaps we can cut it down further.
On 7/8/06, Evan Buswell <[EMAIL PROTECTED]> wrote:
pollThreadEvents could be cut down a little: it
pollThreadEvents could be cut down a little: it is currently being
called both by EvaluationState.executeNext() and
NewlineNodeVisitor.execute() -- meaning it is being called twice when
there is a newline.
Evan
Charles O Nutter wrote:
> I'm starting to run some profiles to find real hotspot probl
Note this was also with my alternative ObjectSpace impl. I'll profile with the old version to see if it comes back up into the hot spots.On 7/8/06, Charles O Nutter
<[EMAIL PROTECTED]> wrote:
I'm starting to run some profiles to find real hotspot problems. So here's the first summary of findings.P
I'm starting to run some profiles to find real hotspot problems. So here's the first summary of findings.Profiling: today's code, gem install --force rake (gem cached locally), up to some time during ri generation (killed after an hour)
This profiling run just examined CPU times for various method
