On July 15, 2015 3:42:17 AM CDT, Yicong Huang wrote:
>Great thanks!
>We tried gc log, and got a piece of below output.
>However, it is hard to read.
>Is it possible to get some common metrics, e.g. timestamp of GC
>occourred,
>gc paused time, gc count?
>We found there is a tool gcanalyze.py migh
so in the part you pasted, the hex numbers are timestamps (I think
they're hex-encoded cycle counts), the numbers you have to fish from
text, but that's enough to say when it started and when it ended. if
you run PYPYLOG=log, you can use logparser to display total time spent
in GC (they all require
Great thanks!
We tried gc log, and got a piece of below output.
However, it is hard to read.
Is it possible to get some common metrics, e.g. timestamp of GC occourred,
gc paused time, gc count?
We found there is a tool gcanalyze.py might help. But the tool depends on
rpython module.
How to run the
PYPYLOG=gc:- would give you some idea, but nothing that can help you
tune the GC. We usually just measure total time with various GC
parameters
On Wed, Jul 15, 2015 at 9:59 AM, Yicong Huang wrote:
> From the document, we saw there are some GC tuning parameters.
> But we've no ideas how to evaluat
>From the document, we saw there are some GC tuning parameters.
But we've no ideas how to evaluate the tuning.
As for java, it is able to output friendly gc log.
Are there any similar output avaiable in pypy?
___
pypy-dev mailing list
pypy-dev@python.org