Hi everyone,
I would like to ask a question about an issue that we faced regarding profiling
memory usage:
We have implemented a custom memory profiler using
`PyMem_GetAllocator/PyMem_SetAllocator` APIs like `tracemalloc`. Right now, we
are facing an issue with numpy: numpy seems to have its o
> In other words, the allocators are concerned about
> memory, not tracing or anything else that can be done by overriding them.
Ok I now understand that `tracemalloc`'s use of allocator APIs is just an
implementation detail. Allocator APIs were used for tracing but they are not
designed for tha
Python version to version and also I think there is no way of getting named
arguments...
I have been dealing with this for a while, so there might be unclear points
in my explanation. I would really appreciate if anyone can help me on a
correct direction on this.
Thanks,
Best Regards.
--
Sümer Cip
modified in many places?
I have been playing with this module only lately on tracemalloc, so please
correct if a major piece is missing in my example or my understanding is
wrong in some way.
Thanks as always!
--
Sümer Cip
___
Python-Dev mai
Thanks Victor, I have a better understanding of tracemalloc internals.
On Tue, Nov 19, 2019 at 10:07 PM Victor Stinner wrote:
> Hi,
>
> Le mar. 19 nov. 2019 à 18:33, Sümer Cip a écrit :
> > First of all, I would like to thank for such a useful tool for debugging
> memory i
Hi there,
yappi(Yet Another Python Profiler) is a multithreaded profiler for 2.x
series(do not know if it will work on 3k, not tested yet). I have done my
best to make it efficient as possible.(details are under the technical
bullet in the website). It is aimed for long-running programs, to
attach
Hi,
While porting a C extension from 2 to 3, I realized that there are some
general cases which can be automated. For example, for my specific
application (yappi - http://code.google.com/p/yappi/), all I need to do is
following things:
1) define PyModuleDef
2) change PyString_AS_STRING calls to
> >
> > 1) define PyModuleDef
> > 2) change PyString_AS_STRING calls to _PyUnicode_AsString
>
> Aside: Please don't use private APIs in Python extensions. Esp.
> the above Unicode API is likely going to be phased out.
>
> You're better off, using PyUnicode_AsUTF8String() instead and
> then leaving
>
> I'm not sure why what C-API is used in Python's extension modules
> needs to be anyway to you.
>
I just tought it is a better programming practice to decrease/narrow inter
modular usage of functions inside the whole dist. and also a good example
for the other 3rd party C Extension developers.
Hi all,
Is there a reason behind the fact that the Python profilers work with Wall
time by default? There are OS-dependent ways to get the CPU time of a
thread, and giving that choice to the user _somehow_ ( to use wall vs cpu
time) might be a good feature?
--
Sumer Cip
__
>
> The original reason was that the Unix wall clock was more accurate
> than its CPU clock. If that's changed we should probably (perhaps in a
> platform-dependent way) change the default to the most accurate clock
> available.
>
>
Currently it seems clock_gettime() APIs have nanosecond resolution
n really not have any use case
for this functionality, ...
--
Sümer Cip
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
12 matches
Mail list logo
