[Python-Dev] [RELEASE] Python 3.8.0b2 is now available for testing

After a few days of delay, but somewhat cutely timed with the US Independence Day, I present you Python 3.8.0b2: https://www.python.org/downloads/release/python-380b2/ This release is the second of four planned beta release previews.

[Python-Dev] Re: Change SystemError to NOT inherit from Exception

Jeroen Demeyer wrote: > On 2019-07-02 23:29, Brett Cannon wrote: > > But two, this would be a semantic shift of what > > classes directly inherit from BaseException. > > It depends how you interpret that. I always interpreted classes > inheriting directly from BaseException as exceptions that you

[Python-Dev] Re: obmalloc (was Have a big machine and spare time? Here's a possible Python bug.)

[Victor Stinner ] > I guess that INADA-san used pyperformance --track-memory. > > pyperf --track-memory doc: > "--track-memory: get the memory peak usage. it is less accurate than > tracemalloc, but has a lower overhead. On Linux, compute the sum of > Private_Clean and Private_Dirty memory

[Python-Dev] Re: obmalloc (was Have a big machine and spare time? Here's a possible Python bug.)

I found calibrated loop count is not stable so memory usage is very different in some benchmarks. Especially, RAM usage of logging benchmark is very relating to loop count: $ PYTHONMALLOC=malloc LD_PRELOAD=$HOME/local/lib/libmimalloc.so ./python bm_logging.py simple --track-memory --fast

[Python-Dev] Re: obmalloc (was Have a big machine and spare time? Here's a possible Python bug.)

I guess that INADA-san used pyperformance --track-memory. pyperf --track-memory doc: "--track-memory: get the memory peak usage. it is less accurate than tracemalloc, but has a lower overhead. On Linux, compute the sum of Private_Clean and Private_Dirty memory mappings of /proc/self/smaps. On

[Python-Dev] Re: obmalloc (was Have a big machine and spare time? Here's a possible Python bug.)

[Antoine Pitrou ] >> Ah, interesting. Were you able to measure the memory footprint as well? [Inada Naoki ] > Hmm, it is not good. mimalloc uses MADV_FREE so it may affect to some > benchmarks. I will look it later. > > ``` > $ ./python -m pyperf compare_to pymalloc-mem.json mimalloc-mem.json

[Python-Dev] Re: obmalloc (was Have a big machine and spare time? Here's a possible Python bug.)

On Thu, 4 Jul 2019 23:32:55 +0900 Inada Naoki wrote: > On Thu, Jul 4, 2019 at 8:09 PM Antoine Pitrou wrote: > > > > Ah, interesting. Were you able to measure the memory footprint as well? > > > > Hmm, it is not good. mimalloc uses MADV_FREE so it may affect to some > benchmarks. I will

[Python-Dev] Re: obmalloc (was Have a big machine and spare time? Here's a possible Python bug.)

On Thu, Jul 4, 2019 at 8:09 PM Antoine Pitrou wrote: > > Ah, interesting. Were you able to measure the memory footprint as well? > Hmm, it is not good. mimalloc uses MADV_FREE so it may affect to some benchmarks. I will look it later. ``` $ ./python -m pyperf compare_to pymalloc-mem.json

[Python-Dev] Re: obmalloc (was Have a big machine and spare time? Here's a possible Python bug.)

On Thu, 4 Jul 2019 16:19:52 +0900 Inada Naoki wrote: > On Tue, Jun 25, 2019 at 5:49 AM Antoine Pitrou wrote: > > > > > > For the record, there's another contender in the allocator > > competition now: > > https://github.com/microsoft/mimalloc/ > > > > Regards > > > > Antoine. > > It's a very

[Python-Dev] Re: obmalloc (was Have a big machine and spare time? Here's a possible Python bug.)

On Tue, Jun 25, 2019 at 5:49 AM Antoine Pitrou wrote: > > > For the record, there's another contender in the allocator > competition now: > https://github.com/microsoft/mimalloc/ > > Regards > > Antoine. It's a very strong competitor! $ ./python -m pyperf compare_to pymalloc.json mimalloc.json