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 rpython, you need a pypy checkout and
PYTHONPATH)
On Wed, Jul 15, 2015 at 10:42 AM, Yicong Huang <hengha....@gmail.com> 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 might help. But the tool depends on
> rpython module.
> How to run the tool?
>
> starting gc state: SCANNING
> stopping, now in gc state: MARKING
> [1cca56e7e5d61f] gc-collect-step}
> [1cca56e7e63793] {gc-collect-step
> starting gc state: MARKING
> number of objects to mark 158 plus 59
> stopping, now in gc state: SWEEPING
> [1cca56e820f113] gc-collect-step}
> [1cca56e8218863] {gc-collect-step
> starting gc state: SWEEPING
>
>
> On Wed, Jul 15, 2015 at 4:03 PM, Maciej Fijalkowski <fij...@gmail.com>
> wrote:
>>
>> 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 <hengha....@gmail.com>
>> wrote:
>> > 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
>> > https://mail.python.org/mailman/listinfo/pypy-dev
>> >
>
>
_______________________________________________
pypy-dev mailing list
pypy-dev@python.org
https://mail.python.org/mailman/listinfo/pypy-dev
