Re: Speed regression from 3.2 to 3.3

[Matt Austern <austern at apple dot com>]

On Monday, January 20, 2003, at 11:57 PM, Jan Hubicka wrote:

> > You could try to reverse gc changes to its 3.2 version and look wether
> > time spent in gc decreases or not...
> This is quite dificult to do as large parts of PCH branch has been
> merged to 3.3.  Can you just take a look at 3.2 time and mem reports 
> and
> looks what has changed to have something to start with?
What I see from the time report is pretty much what I said before: the
parser and the gc have gone up dramatically, nothing else matters.
I'm attaching a graph, for those who are interested.

I'm especially interested in the gc numbers, since it's hard to imagine
any good reason for why they went up.

Mem report shows...  Well, one thing it shows is that the per-node
statistics (how many nodes of each type got allocated) have
disappeared in 3.3 and 3.4.  Was that intentional?

I didn't see anything particularly interesting in the mem_report
information that I do have.  I'm attaching the output it; perhaps
someone else will see more than I did.  But at this point I still don't
know whether the gc time shot up because the gc is suddenly dealing
with lots more memory, or whether there's just a simple bug in the
collector.

			--Matt

Attachment: timings.pdf
Description: Adobe PDF document

Attachment: memreport.txt
Description: Text document