On July 15, 2015 3:42:17 AM CDT, 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?
Grab the PyPy source. The rpython module is inside it.
>
>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
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
_______________________________________________
pypy-dev mailing list
pypy-dev@python.org
https://mail.python.org/mailman/listinfo/pypy-dev
