[pypy-dev] pypy-2.3.1 memory profiling strategies

jim horng jimhorng at gmail.com
Sun Aug 2 08:57:34 CEST 2015


Hi Phyo,
thanks for prompt response :)
I didn't state clear that I already tried periodic gc but memory usage
still increase over team till out of memory, so we assume it's a real leak
cause by python program but we don't have good tool/methodology to hunt it,
thanks :)

Best Regards,
Jim(洪懷謙)

On Sun, Aug 2, 2015 at 4:35 AM, Phyo Arkar <phyo.arkarlwin at gmail.com> wrote:

> Memory handling is improved on 2.6.1 , theres no memory leak there. we
> running for 2 months already.
> You gotta upgrade.
>
> On Fri, Jul 31, 2015 at 3:51 PM, jim horng <jimhorng at gmail.com> wrote:
>
>> Hi all,
>> Not sure if it's appropriate to post here since there's no pypy-user
>> group :)
>> My question is as title, we got memory leak on pypy process and process
>> will down when out of memory, only on production site.
>> Our simplified environment as below:
>> * OS: Centos 6
>> * pypy-2.3.1
>>
>> objgraph is seems the only profiling library we can use in this env, and
>> only with its partial function of printing all current objects in memory
>> instead of any further info such as references (.getrefcount not
>> implemented).
>> It turns out we can only see lots of "int", "str", "list" objects seems
>> leaking rather than knowing who are using them or whom they are using. :(
>>
>> Our constraint are
>> * it's hard to change production python runtime since it might affect to
>> our users
>> * we cannot reproduce on other environment
>>
>> "pmap" produced data only shows memory growing in a [anon] block.
>>
>> Please advise if there's other tool/methodologies to attack this problem,
>> thanks a lot in advance :)
>>
>> Best Regards,
>> Jim(洪懷謙)
>>
>> _______________________________________________
>> pypy-dev mailing list
>> pypy-dev at python.org
>> https://mail.python.org/mailman/listinfo/pypy-dev
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pypy-dev/attachments/20150802/355bfaec/attachment.html>


More information about the pypy-dev mailing list