Open GoogleCodeExporter opened 8 years ago
The initial amount of data returned to the browser when loading a cachegrind
file is determined by the number of different functions
called in the profiled script. In other words the amount of data returned does
not depend directly on the size of the cachegrind file.
What does depend on the size of the cachegrind file is the time it takes to
preprocess the file. The preprocessing is done one time for
each profile and the result is cached in a temp file.
On my, reasonably fast, computer preprocessing 60MB and larger profiles works
fine. So I suspect that something else is causing your
problem.
Are you having this problem with all profiles of this size or is this the only
one you have tried?
Original comment by oett...@gmail.com
on 15 Mar 2009 at 2:11
I have seen a similar problem w/a heavy cachegrind file... only 11MB in size,
but some
functions get called 11,000 times and apache ends up eating all available RAM.
I
suspect this is just a function of loading all those calls into memory than an
actual
issue with webgrind, but I haven't looked into it deeper. The next time it
happens
I'll attach an example cachegrind file.
Original comment by gguzman....@gmail.com
on 9 Dec 2009 at 1:39
Original comment by gugakf...@gmail.com
on 27 Oct 2010 at 10:49
Original issue reported on code.google.com by
T.Hamb...@gmail.com
on 12 Mar 2009 at 11:15