[issue6942] email.generator.Generator memory consumption

Change by Irit Katriel : -- stage: -> resolved status: pending -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue6942] email.generator.Generator memory consumption

Irit Katriel added the comment: Ross, the link to your code no longer works. Do you still have it, and if so could you paste/upload it here? -- nosy: +iritkatriel status: open -> pending ___ Python tracker

Re: memory consumption

> I had the (mis)pleasure of dealing with a multi-terabyte postgresql > instance many years ago and figuring out why random scripts were eating > up system memory became quite common. > > All of our "ETL" scripts were either written in Perl, Java, or Python > but the results were always the

Re: memory consumption

On 3/29/21 5:12 AM, Alexey wrote: Hello everyone! I'm experiencing problems with memory consumption. I have a class which is doing ETL job. What`s happening inside: - fetching existing objects from DB via SQLAchemy - iterate over raw data - create new/update existing objects - commit

Re: memory consumption

четверг, 1 апреля 2021 г. в 15:56:23 UTC+3, Marco Ippolito: > > > Are you running with systemd? > > > > I really don't know. > An example of how to check: > > ``` > $ readlink /sbin/init > /lib/systemd/systemd > ``` > > You want to check which program runs as PID 1. Thank you Marco --

Re: memory consumption

четверг, 1 апреля 2021 г. в 15:46:21 UTC+3, Marco Ippolito: > I suspect the high watermark of `` needs to be reachable still and, > secondly, that a forceful constraint whilst running would crash the > container? Exactly. -- https://mail.python.org/mailman/listinfo/python-list

Re: memory consumption

четверг, 1 апреля 2021 г. в 17:21:59 UTC+3, Mats Wichmann: > On 4/1/21 5:50 AM, Alexey wrote: > > Found it. As I said before the problem was lurking in the cache. > > Few days ago I read about circular references and things like that and > > I thought to myself that it might be the case. To

Re: memory consumption

четверг, 1 апреля 2021 г. в 16:02:15 UTC+3, Barry: > > On 1 Apr 2021, at 13:46, Marco Ippolito wrote: > > > > > >> > What if you increase the machine's (operating system's) swap space? Does > that take care of the problem in practice? > >>> > >>> I can`t do that because it will

Re: memory consumption

четверг, 1 апреля 2021 г. в 15:27:01 UTC+3, Chris Angelico: > On Thu, Apr 1, 2021 at 10:56 PM Alexey wrote: > > > > Found it. As I said before the problem was lurking in the cache. > > Few days ago I read about circular references and things like that and > > I thought to myself that it might

Re: memory consumption

On 4/1/21 5:50 AM, Alexey wrote: Found it. As I said before the problem was lurking in the cache. Few days ago I read about circular references and things like that and I thought to myself that it might be the case. To build the cache I was using lots of 'setdefault' methods chained together

Re: memory consumption

> On 1 Apr 2021, at 13:46, Marco Ippolito wrote: > >  >> What if you increase the machine's (operating system's) swap space? Does that take care of the problem in practice? >>> >>> I can`t do that because it will affect other containers running on this >>> host. >>> In my opinion

Re: memory consumption

> > Are you running with systemd? > > I really don't know. An example of how to check: ``` $ readlink /sbin/init /lib/systemd/systemd ``` You want to check which program runs as PID 1. ``` ps 1 ``` -- https://mail.python.org/mailman/listinfo/python-list

Re: memory consumption

четверг, 1 апреля 2021 г. в 14:57:29 UTC+3, Barry: > > On 31 Mar 2021, at 09:42, Alexey wrote: > > > > среда, 31 марта 2021 г. в 01:20:06 UTC+3, Dan Stromberg: > >>> On Tue, Mar 30, 2021 at 1:25 AM Alexey wrote: > >>> > >>> > >>> I'm sorry. I didn't understand your question right. If I have

Re: memory consumption

> >> What if you increase the machine's (operating system's) swap space? Does > >> that take care of the problem in practice? > > > > I can`t do that because it will affect other containers running on this > > host. > > In my opinion it may significantly reduce their performance. > > Assuming

Re: memory consumption

On Thu, Apr 1, 2021 at 10:56 PM Alexey wrote: > > Found it. As I said before the problem was lurking in the cache. > Few days ago I read about circular references and things like that and > I thought to myself that it might be the case. To build the cache I was > using lots of 'setdefault'

Re: memory consumption

> On 31 Mar 2021, at 09:42, Alexey wrote: > > среда, 31 марта 2021 г. в 01:20:06 UTC+3, Dan Stromberg: >>> On Tue, Mar 30, 2021 at 1:25 AM Alexey wrote: >>> >>> >>> I'm sorry. I didn't understand your question right. If I have 4 workers, >>> they require 4Gb >>> in idle state and some

Re: memory consumption

Found it. As I said before the problem was lurking in the cache. Few days ago I read about circular references and things like that and I thought to myself that it might be the case. To build the cache I was using lots of 'setdefault' methods chained together self.__cache.setdefault(cluster_name,

Re: memory consumption

On 31/03/2021 09:35, Alexey wrote: среда, 31 марта 2021 г. в 01:20:06 UTC+3, Dan Stromberg: What if you increase the machine's (operating system's) swap space? Does that take care of the problem in practice? I can`t do that because it will affect other containers running on this host. In my

Re: memory consumption

среда, 31 марта 2021 г. в 18:17:46 UTC+3, Dieter Maurer: > Alexey wrote at 2021-3-31 02:43 -0700: > >среда, 31 марта 2021 г. в 06:54:52 UTC+3, Inada Naoki: > > ... > >> You can get some hints from sys._debugmallocstats(). It prints > >> obmalloc (allocator for small objects) stats to stderr. >

Re: memory consumption

Alexey wrote at 2021-3-31 02:43 -0700: >среда, 31 марта 2021 г. в 06:54:52 UTC+3, Inada Naoki: > ... >> You can get some hints from sys._debugmallocstats(). It prints >> obmalloc (allocator for small objects) stats to stderr. >> Try printing stats before and after 1st run, and after 2nd run. And

Re: memory consumption

среда, 31 марта 2021 г. в 14:16:30 UTC+3, Inada Naoki: > > ** Before first run: > > # arenas allocated total = 776 > > # arenas reclaimed = 542 > > # arenas highwater mark = 234 > > # arenas allocated current = 234 > > 234 arenas * 262144 bytes/arena = 61,341,696 > > ** After

Re: memory consumption

> ** Before first run: > # arenas allocated total = 776 > # arenas reclaimed = 542 > # arenas highwater mark= 234 > # arenas allocated current = 234 > 234 arenas * 262144

Re: memory consumption

среда, 31 марта 2021 г. в 11:52:43 UTC+3, Marco Ippolito: > > > At which point does the problem start manifesting itself? > > The problem spot is my cache(dict). I simplified my code to just load > > all the objects to this dict and then clear it. > What's the memory utilisation just _before_

Re: memory consumption

среда, 31 марта 2021 г. в 06:54:52 UTC+3, Inada Naoki: > First of all, I recommend upgrading your Python. Python 3.6 is a bit old. I was thinking about that. > As you saying, Python can not return the memory to OS until the whole > arena become unused. > If your task releases all objects

Re: memory consumption

среда, 31 марта 2021 г. в 05:45:27 UTC+3, cameron...@gmail.com: > Since everyone is talking about vague OS memory use and not at all about > working set size of Python objects, let me ... > On 29Mar2021 03:12, Alexey wrote: > >I'm experiencing problems with memory consumption.

Re: memory consumption

> > At which point does the problem start manifesting itself? > The problem spot is my cache(dict). I simplified my code to just load > all the objects to this dict and then clear it. What's the memory utilisation just _before_ performing this load? I am assuming it's much less than this 1 GB

Re: memory consumption

среда, 31 марта 2021 г. в 01:20:06 UTC+3, Dan Stromberg: > On Tue, Mar 30, 2021 at 1:25 AM Alexey wrote: > > > > > I'm sorry. I didn't understand your question right. If I have 4 workers, > > they require 4Gb > > in idle state and some extra memory when they execute other tasks. If I > >

Re: memory consumption

вторник, 30 марта 2021 г. в 18:43:54 UTC+3, Alan Gauld: > On 29/03/2021 11:12, Alexey wrote: > The first thing you really need to tell us is which > OS you are using? Memory management varies wildly > depending on OS. Even different flavours of *nix > do it differently. I'm using

Re: memory consumption

вторник, 30 марта 2021 г. в 18:43:51 UTC+3, Marco Ippolito: > Have you tried to identify where in your code the surprising memory > allocations > are made? Yes. > You could "bisect search" by adding breakpoints: > > https://docs.python.org/3/library/functions.html#breakpoint > > At which

Re: memory consumption

On Mon, Mar 29, 2021 at 7:16 PM Alexey wrote: > > Problem. Before executing, my interpreter process weighs ~100Mb, after first > run memory increases up to 500Mb > and after second run it weighs 1Gb. If I will continue to run this class, > memory wont increase, so I think > it's not a memory

Re: memory consumption

Since everyone is talking about vague OS memory use and not at all about working set size of Python objects, let me ... On 29Mar2021 03:12, Alexey wrote: >I'm experiencing problems with memory consumption. > >I have a class which is doing ETL job. What`s happening inside: > - fetch

Re: memory consumption

On Tue, Mar 30, 2021 at 1:25 AM Alexey wrote: > > I'm sorry. I didn't understand your question right. If I have 4 workers, > they require 4Gb > in idle state and some extra memory when they execute other tasks. If I > increase workers > count up to 16, they`ll eat all the memory I have (16GB) on

Re: memory consumption

On 30/03/2021 16:50, Chris Angelico wrote: >> A 1GB process on modern computers is hardly a big problem? >> Most machines have 4G and many have 16G or even 32G >> nowadays. >> > > Desktop systems maybe, but if you rent yourself a worker box, it might > not have anything like that much.

Re: memory consumption

On Wed, Mar 31, 2021 at 2:44 AM Alan Gauld via Python-list wrote: > > On 29/03/2021 11:12, Alexey wrote: > > Hello everyone! > > I'm experiencing problems with memory consumption. > > > > The first thing you really need to tell us is which > OS you are using

Re: memory consumption

Have you tried to identify where in your code the surprising memory allocations are made? You could "bisect search" by adding breakpoints: https://docs.python.org/3/library/functions.html#breakpoint At which point does the problem start manifesting itself? --

Re: memory consumption

On 29/03/2021 11:12, Alexey wrote: > Hello everyone! > I'm experiencing problems with memory consumption. > The first thing you really need to tell us is which OS you are using? Memory management varies wildly depending on OS. Even different flavours of *nix do it differently. However

Re: memory consumption

> I'm sorry. I didn't understand your question right. If I have 4 workers, > they require 4Gb > in idle state and some extra memory when they execute other tasks. If I > increase workers > count up to 16, they`ll eat all the memory I have (16GB) on my machine and > will crash as soon > as system

Re: memory consumption

понедельник, 29 марта 2021 г. в 19:56:52 UTC+3, Stestagg: > > > 2. Can you try a test with 16 or 32 active workers (i.e. number of > > > workers=2x available memory in GB), do they all still end up with 1gb > > > usage? or do you get any other memory-related issues running this? > > Yes. They

Re: memory consumption

ry management via the envvar > `MALLOC_ARENA_MAX` to use a common memory pool (called "arena") > for all threads. > It is known that this can drastically reduce memory consumption > in multi thread systems. Tried with this variable. No luck. Thanks anyway. -- https://mail.python.org/mailman/listinfo/python-list

Re: memory consumption

> > 2. Can you try a test with 16 or 32 active workers (i.e. number of > > workers=2x available memory in GB), do they all still end up with 1gb > > usage? or do you get any other memory-related issues running this? > Yes. They will consume 1Gb each. It doesn't matter how many workers I > have, >

Re: memory consumption

In production I have 8 workers, > so in idle they will hold 8Gb. Depending on your system (this works for `glibc` systems), you can instruct the memory management via the envvar `MALLOC_ARENA_MAX` to use a common memory pool (called "arena") for all threads. It is known that this can dra

Re: memory consumption

понедельник, 29 марта 2021 г. в 17:19:02 UTC+3, Stestagg: > On Mon, Mar 29, 2021 at 2:32 PM Alexey wrote: > Some questions here to help understand more: > > 1. Do you have any actual problems caused by running 8 celery workers > (beyond high memory reports)? What are they? No. Everything

Re: memory consumption

On Mon, Mar 29, 2021 at 2:32 PM Alexey wrote: > понедельник, 29 марта 2021 г. в 15:57:43 UTC+3, Julio Oña: > > It looks like the problem is on celery. > > The mentioned issue is still open, so not sure if it was corrected. > > > > https://manhtai.github.io/posts/memory-leak-in-celery/ > > As I

Re: memory consumption

понедельник, 29 марта 2021 г. в 15:57:43 UTC+3, Julio Oña: > It looks like the problem is on celery. > The mentioned issue is still open, so not sure if it was corrected. > > https://manhtai.github.io/posts/memory-leak-in-celery/ As I mentioned in my first message, I tried to run this

Re: memory consumption

It looks like the problem is on celery. The mentioned issue is still open, so not sure if it was corrected. https://manhtai.github.io/posts/memory-leak-in-celery/ Julio El lun, 29 de mar. de 2021 a la(s) 08:31, Alexey (zen.supag...@gmail.com) escribió: > Hello Lars! > Thanks for your

Re: memory consumption

Hello Lars! Thanks for your interest. The problem appears when all celery workers require 1Gb of RAM each in idle state. They hold this memory constantly and when they do something useful, they grab more memory. I think 8Gb+ in idle state is quite a lot for my app. > Did it crash your system or

Re: memory consumption

that there can be (good) reasons to care, but as long as your tasks run fine, without clogging your system, in my opinion there might be nothing to worry about. Cheers Lars Am 29.03.21 um 12:12 schrieb Alexey: > Hello everyone! > I'm experiencing problems with memory consumption. > > I

memory consumption

Hello everyone! I'm experiencing problems with memory consumption. I have a class which is doing ETL job. What`s happening inside: - fetching existing objects from DB via SQLAchemy - iterate over raw data - create new/update existing objects - commit changes Before processing data I create

[issue26415] Excessive peak memory consumption by the Python parser

Pablo Galindo Salgado added the comment: Closing as we have a new parser in 3.9 and the current one will be removed in Python 3.10. -- resolution: -> rejected stage: patch review -> resolved status: open -> closed ___ Python tracker

[issue39146] too much memory consumption in re.compile unicode

Zachary Ware added the comment: As mentioned on the attached PR, Python 2.7 has reached EOL and this can no longer be accepted. Thanks for the report and patch anyway! -- nosy: +zach.ware resolution: -> out of date stage: patch review -> resolved status: open -> closed

[issue39146] too much memory consumption in re.compile unicode

Change by Andy Lester : -- components: +Regular Expressions -Library (Lib) nosy: +ezio.melotti, mrabarnett ___ Python tracker ___

[issue39146] too much memory consumption in re.compile unicode

Zhipeng Xie <775350...@qq.com> added the comment: > but range() was here before ebd48b4f650d. before ebd48b4f650d, _optimize_unicode use xrange. So python2.7.8 is ok and python2.7.9 consume much memory in my test case. > Obviously there are other causes of the difference between 2.7 and 3.x.

[issue39146] too much memory consumption in re.compile unicode

in comparison with total memory consumption. Obviously there are other causes of the difference between 2.7 and 3.x. -- ___ Python tracker <https://bugs.python.org/issue39

[issue39146] too much memory consumption in re.compile unicode

Zhipeng Xie <775350...@qq.com> added the comment: Hi, I tracked it down and found that this problem was introduced in python2.7.9 by following commit: https://hg.python.org/cpython/rev/ebd48b4f650d -- nosy: +serhiy.storchaka ___ Python tracker

[issue39146] too much memory consumption in re.compile unicode

Change by Roundup Robot : -- keywords: +patch pull_requests: +17172 stage: -> patch review pull_request: https://github.com/python/cpython/pull/17728 ___ Python tracker ___

[issue39146] too much memory consumption in re.compile unicode

Change by Zhipeng Xie <775350...@qq.com>: -- title: to much memory consumption in re.compile unicode -> too much memory consumption in re.compile unicode ___ Python tracker <https://bugs.python.or

[issue39146] to much memory consumption in re.compile unicode

20 0 28032 8880 4868 S 0.0 0.1 0:00.02 python3 -- components: Library (Lib) messages: 358936 nosy: Zhipeng Xie priority: normal severity: normal status: open title: to much memory consumption in re.compile unicode type: resource usage versions: Pyth

[issue26415] Excessive peak memory consumption by the Python parser

Change by Inada Naoki : -- nosy: +inada.naoki ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue26415] Excessive peak memory consumption by the Python parser

Change by Pablo Galindo Salgado : -- nosy: +pablogsal ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue26415] Excessive peak memory consumption by the Python parser

Change by Serhiy Storchaka : -- assignee: -> serhiy.storchaka ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue26415] Excessive peak memory consumption by the Python parser

A. Skrobov added the comment: I've run pyperformance (0.7.0) with my updated patch, and posted results at the PR page. They look encouraging enough. -- ___ Python tracker

[issue26415] Excessive peak memory consumption by the Python parser

A. Skrobov added the comment: @Serhiy: incredibly, this patch from 2.5 years ago required very minor changes to apply to the latest master. Shows how ossified the parser is :-) Now posted as https://github.com/python/cpython/pull/10995 -- ___

[issue26415] Excessive peak memory consumption by the Python parser

Change by Roundup Robot : -- keywords: +patch pull_requests: +10236 ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue26415] Excessive peak memory consumption by the Python parser

Change by Brett Cannon : -- nosy: -brett.cannon ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue26415] Excessive peak memory consumption by the Python parser

Change by Giampaolo Rodola' : -- nosy: -giampaolo.rodola ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue26415] Excessive peak memory consumption by the Python parser

Serhiy Storchaka added the comment: Do you mind to create a pull request for reviewing? I can not promise that it will be merged, but it will have a chance. For reference, the article about this patch (on Russian): https://habr.com/post/314062/ . -- versions: +Python 3.8 -Python

Re: why does memory consumption keep growing?

On Fri, Oct 6, 2017 at 8:05 PM, D'Arcy Cain wrote: > On 10/05/2017 05:42 PM, Fetchinson . via Python-list wrote: >> >> On 10/5/17, Chris Angelico wrote: >>> >>> On Fri, Oct 6, 2017 at 8:06 AM, Fetchinson . via Python-list >>>

Re: why does memory consumption keep growing?

On 10/05/2017 05:42 PM, Fetchinson . via Python-list wrote: On 10/5/17, Chris Angelico wrote: On Fri, Oct 6, 2017 at 8:06 AM, Fetchinson . via Python-list wrote: import mystuff mystuff.some_more_expensive_stuff( x ) del mystuff

Re: why does memory consumption keep growing?

On 6 October 2017 at 06:51, Chris Angelico wrote: > Cloud computing is the answer. > > If you don't believe me, just watch the sky for a while - new clouds > get added without the sky turning off and on again. The sky reboots every 24 hours, and the maintenance window's about

Re: why does memory consumption keep growing?

Chris Angelico wrote: > On Fri, Oct 6, 2017 at 4:14 PM, Gregory Ewing > wrote: >> Steve D'Aprano wrote: >>> >>> Plus the downtime and labour needed to install the memory, if the >>> computer will even take it. >> >> >> Obviously we need an architecture that supports

Re: why does memory consumption keep growing?

On Fri, 6 Oct 2017 04:51 pm, Chris Angelico wrote: > On Fri, Oct 6, 2017 at 4:14 PM, Gregory Ewing > wrote: >> Steve D'Aprano wrote: >>> >>> Plus the downtime and labour needed to install the memory, if the computer >>> will even take it. >> >> >> Obviously we need

Re: why does memory consumption keep growing?

On Fri, Oct 6, 2017 at 4:14 PM, Gregory Ewing wrote: > Steve D'Aprano wrote: >> >> Plus the downtime and labour needed to install the memory, if the computer >> will even take it. > > > Obviously we need an architecture that supports hot-swappable > robot-installable

Re: why does memory consumption keep growing?

Steve D'Aprano wrote: Plus the downtime and labour needed to install the memory, if the computer will even take it. Obviously we need an architecture that supports hot-swappable robot-installable RAM. -- Greg -- https://mail.python.org/mailman/listinfo/python-list

Re: why does memory consumption keep growing?

mory. As you'll > see I tried to make every attempt at removing everything at the end of > each cycle so that memory consumption doesn't grow as the for loop > progresses, but it still does. > > import os > > for f in os.listdir( '.' ): > > x = [ ] >

Re: why does memory consumption keep growing?

n takes about 5-10 MB of memory. As you'll > see I tried to make every attempt at removing everything at the end of > each cycle so that memory consumption doesn't grow as the for loop > progresses, but it still does. > > import os > > for f in os.listdir( '.' ): > > x = [

Re: why does memory consumption keep growing?

ee I tried to make every attempt at removing everything at the end of > each cycle so that memory consumption doesn't grow as the for loop > progresses, but it still does. How do you know memory consumption is still growing? I'm not saying it isn't, but knowing what the symptoms are and how y

Re: why does memory consumption keep growing?

nd each operation takes about 5-10 MB of memory. As you'll >>see I tried to make every attempt at removing everything at the end of >>each cycle so that memory consumption doesn't grow as the for loop >>progresses, but it still does. > > "2x 8GB DIMM DDR3-1600" cost $95.

Re: why does memory consumption keep growing?

emory. As you'll see I tried to make every attempt at removing everything at the end of each cycle so that memory consumption doesn't grow as the for loop progresses, but it still does. "2x 8GB DIMM DDR3-1600" cost $95.99 according to a web page. This might be in the order of ma

Re: why does memory consumption keep growing?

at removing everything at the end of each cycle so that memory consumption doesn't grow as the for loop progresses, but it still does. import os for f in os.listdir( '.' ): x = [ ] for ( i, line ) in enumerate( open( f ) ): import mystuff x.append( mystuff.expensive_stuff

Re: why does memory consumption keep growing?

oes some operation on them, and then quits. There are 500 files >> involved and each operation takes about 5-10 MB of memory. As you'll >> see I tried to make every attempt at removing everything at the end of >> each cycle so that memory consumption doesn't grow as the for loop >> progre

Re: why does memory consumption keep growing?

n takes about 5-10 MB of memory. As you'll > see I tried to make every attempt at removing everything at the end of > each cycle so that memory consumption doesn't grow as the for loop > progresses, but it still does. > > import os > > for f in os.listdir( '.' ): > > x

Re: why does memory consumption keep growing?

at the end of each cycle so that memory consumption doesn't grow as the for loop progresses, but it still does. import os for f in os.listdir( '.' ): x = [ ] for ( i, line ) in enumerate( open( f ) ): import mystuff x.append( mystuff.expensive_stuff( line

why does memory consumption keep growing?

so that memory consumption doesn't grow as the for loop progresses, but it still does. import os for f in os.listdir( '.' ): x = [ ] for ( i, line ) in enumerate( open( f ) ): import mystuff x.append( mystuff.expensive_stuff( line ) ) del mystuff import

[issue26415] Excessive peak memory consumption by the Python parser

A. Skrobov added the comment: To bump this year-old issue, I have delivered a talk at EuroPython 2017, explaining what my patch does, how it does what it does, and why it's a good thing to do. You can watch my talk at https://www.youtube.com/watch?v=dyRDmcsTwhE=1h52m38s --

[issue26415] Excessive peak memory consumption by the Python parser

Changes by Charalampos Stratakis : -- nosy: +cstratak ___ Python tracker ___ ___

[issue26415] Excessive peak memory consumption by the Python parser

Changes by Petr Viktorin : -- nosy: +encukou ___ Python tracker ___ ___ Python-bugs-list

[issue28509] Key-sharing dictionaries can inrease the memory consumption

Changes by Xiang Zhang : -- nosy: +xiang.zhang ___ Python tracker ___ ___ Python-bugs-list

[issue28509] Key-sharing dictionaries can inrease the memory consumption

INADA Naoki added the comment: And I feel current target size of dict_merge is bit larger. When inserting new item: * ma_used = dk_size*2 / 3 when right before increasing keys * ma_used = dk_size/ 3 when right after increasing keys On the other hand, current dict_merge creates: * ma_used

[issue28509] Key-sharing dictionaries can inrease the memory consumption

INADA Naoki added the comment: > 0 (128, 60) > 1 (128, 60) > 2 (128, 60) > 3 (128, 60) > 4 (128, 60) > 5 (128, 60) Minimum dict keysize is 8, and it's capacity is 5. > 6 (196, 196) Dict is resized. And since __dict__.update() caused the resizing, both are normal (combined) dict. > 7 (196,

[issue28509] Key-sharing dictionaries can inrease the memory consumption

reter Core messages: 279215 nosy: Mark.Shannon, benjamin.peterson, inada.naoki, rhettinger, serhiy.storchaka priority: normal severity: normal status: open title: Key-sharing dictionaries can inrease the memory consumption type: resource usage ___ Python tracker <

[issue26415] Excessive peak memory consumption by the Python parser

A. Skrobov added the comment: Updated the comment for Init_ValidationGrammar() -- Added file: http://bugs.python.org/file44370/patch ___ Python tracker

[issue26415] Excessive peak memory consumption by the Python parser

A. Skrobov added the comment: Xavier, the big picture description of my patch is in http://bugs.python.org/file43665/devguide_patch The heap fragmentation was observed by Victor, not by myself. Victor, could you please create a new ticket for your python_memleak.py reproducer? --

[issue26415] Excessive peak memory consumption by the Python parser

Xavier Combelle added the comment: Looks that there is two bug as partial solution of the main bug which is reduce memory consumption of the parser: - The compression thing - the reducing of heap fragmentation Could each sub bug have it's own bug tracker and mark them blocking for the main bug

[issue26415] Excessive peak memory consumption by the Python parser

A. Skrobov added the comment: Fixing whitespace in the patch, and including an update for the docs -- Added file: http://bugs.python.org/file43664/patch ___ Python tracker

[issue26415] Excessive peak memory consumption by the Python parser

Changes by A. Skrobov : Added file: http://bugs.python.org/file43665/devguide_patch ___ Python tracker ___

[issue27371] Runaway memory consumption using tkinter update()

Serhiy Storchaka added the comment: Could you please file a report on Tk bugtracker? https://core.tcl.tk/tk/ticket -- ___ Python tracker ___

[issue27371] Runaway memory consumption using tkinter update()

Changes by R. David Murray : -- stage: -> resolved ___ Python tracker ___ ___

[issue27371] Runaway memory consumption using tkinter update()

Jeremy Blow added the comment: Confirmed the problem is with Tk/MacOS. Running a simple TCL script yielded the same behavior in terms of memory. The hunt goes elsewhere... Thank you R. David for the suggestion. ``` package require Tk while 1 { update } ``` # MacOS 10.9.4 /Users/jeremy$

[issue27371] Runaway memory consumption using tkinter update()

Jeremy Blow added the comment: That seems like a good idea, will do so and report back findings. Hey, good meeting you at PyCon, by the way. Met you at the freelance open space. :-) -- ___ Python tracker

[issue27371] Runaway memory consumption using tkinter update()

R. David Murray added the comment: You might want to try stripping it further, and see if you can reproduce it just using tk, without python involved. -- nosy: +r.david.murray title: Runaway memory consumption using update() -> Runaway memory consumption using tkinter upd

  1   2   >