2013/10/31 Victor Stinner :
> Log calls to the memory allocator
> -
>
> A different approach is to log calls to ``malloc()``, ``realloc()`` and
> ``free()`` functions. Calls can be logged into a file or send to another
> computer through the network. Example of a log
New update of the PEP combining various remarks:
* Remove GroupedStats class and Snapshot.group_by(): replaced with a
new Snapshot.statistics() method which combines all features
* Rename reset() to clear_traces() and explain how to get traces
before clearing traces
* Snapshot.apply_filters() now
> Snapshot
>
>
> ``Snapshot(timestamp: datetime.datetime, traceback_limit: int, stats:
> dict=None, traces: dict=None)`` class:
>
> Snapshot of statistics and traces of memory blocks allocated by
> Python.
>
> ``apply_filters(filters)`` method:
>
> Apply filters on the ``traces
2013/10/30 Kristján Valur Jónsson :
> The point of a PEP is getting something into standard python. The command
> line flag is also part of this.
> Piggybacking a lightweight client/server data-gathering version of this on
> top of the PEP
> could be beneficial in that respect.
In my opinion, y
> -Original Message-
> From: Victor Stinner [mailto:victor.stin...@gmail.com]
> Sent: 29. október 2013 21:30
> To: Kristján Valur Jónsson
> Cc: python-dev
> Subject: Re: [Python-Dev] Updated PEP 454 (tracemalloc): no more metrics!
> tracemalloc maintains a dictio
2013/10/26 Kristján Valur Jónsson :
> In that case, how about adding a client/server feature?
>
> If you standardize the format, a minimal tracing client could write a log,
> or send it to a socket, in a way that can be turned into a snapshot by a
> corresponsing utility reading from a file or list
Hum, timestamp and traceback_limit attributed of GroupedStats can also be
removed, they are just of the same attribute of the Snapshot class and
GroupedStats is created from Snapshot.group_by().
Le 27 oct. 2013 17:26, "Victor Stinner" a écrit :
> * do you have a better suggestion for GroupedStats
I updated the PEP according to different comments:
* replace Snapshot.create() class method with take_snapshot() function
* get_traces() now returns a list instead of a dict (remove addresses)
* remove get_stats()
* unknown frames are now stored as ("", 0) instead of (None, None)
* remove get_obje
be a future addition…
From: Python-Dev [mailto:python-dev-bounces+kristjan=ccpgames@python.org]
On Behalf Of Victor Stinner
Sent: 24. október 2013 16:45
To: python-dev
Subject: Re: [Python-Dev] Updated PEP 454 (tracemalloc): no more metrics!
> When I was looking for memory leaks in the re
2013/10/24 Kristján Valur Jónsson :
>
> Now, I would personally not truncate the stack, because I can afford the
> memory,
> but even if I would, for example, to hide a bunch of detail, I would want to
> throw away
> the _lower_ detals of the stack. It is unimportant to me to know if memory
> w
> When I was looking for memory leaks in the regex module I simply wrote
all of the allocations, reallocations and deallocations to a log file and
then parsed it afterwards using a Python script. Simple, but effective.
He he, it's funny because you described exactly my first implementation of
trac
On 24/10/2013 15:40, Kristján Valur Jónsson wrote:
-Original Message-
From: Nick Coghlan [mailto:ncogh...@gmail.com]
Sent: 24. október 2013 12:44
To: Kristján Valur Jónsson
Cc: Python Dev
Subject: Re: [Python-Dev] Updated PEP 454 (tracemalloc): no more metrics!
Not everything is a PC
> -Original Message-
> From: Nick Coghlan [mailto:ncogh...@gmail.com]
> Sent: 24. október 2013 12:44
> To: Kristján Valur Jónsson
> Cc: Python Dev
> Subject: Re: [Python-Dev] Updated PEP 454 (tracemalloc): no more metrics!
> Not everything is a PC that you can just a
2013/10/24 Kristján Valur Jónsson :
>> Test 1. With the Python test suite, 467,738 traces limited to 1 frame:
> ...
>> I'm surprised: it's faster than the benchmark I ran some weeks ago.
>> Maybe I optimized something? The most critical operation, taking a snapshot
>> takes half a second, so it's e
On 24 October 2013 22:34, Kristján Valur Jónsson wrote:
> I understand your desire for things to be fast, but let me just re-iterate my
> view
> that for this kind of jobs, performance is completely secondary. Memory
> debugging and analysis is an off-line, laboratory task. In my opinion,
> per
> -Original Message-
> From: Victor Stinner [mailto:victor.stin...@gmail.com]
> Sent: 24. október 2013 01:03
> To: Kristján Valur Jónsson
> Cc: Python Dev
> Subject: Re: [Python-Dev] Updated PEP 454 (tracemalloc): no more metrics!
>
>
> The use case of get_
Hi,
2013/10/23 Kristján Valur Jónsson :
> This might be a good place to make some comments.
> I have discussed some of this in private with Victor, but wanted to make them
> here, for the record.
Yes, I prefer to discuss the PEP on python-dev. It's nice to get more
feedback, I expect to get a be
This might be a good place to make some comments.
I have discussed some of this in private with Victor, but wanted to make them
here, for the record.
Mainly, I agree with removing code. I'd like to go further, since in my
experience, the less code in C, the better.
1) really, all that is requ
18 matches
Mail list logo
