Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #78927

Re: "High water" Memory fragmentation still a thing?

Path csiph.com!usenet.pasdenom.info!aioe.org!news.stack.nl!newsfeed.xs4all.nl!newsfeed3a.news.xs4all.nl!xs4all!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail
Return-Path <rosuav@gmail.com>
X-Original-To python-list@python.org
Delivered-To python-list@mail.python.org
X-Spam-Status OK 0.081
X-Spam-Evidence '*H*': 0.85; '*S*': 0.01; 'restarted': 0.09; 'subject:skip:f 10': 0.09; 'subject:still': 0.09; 'runs': 0.10; 'cc:addr:python-list': 0.11; 'python': 0.11; 'code),': 0.16; 'consequence,': 0.16; 'from:addr:rosuav': 0.16; 'from:name:chris angelico': 0.16; 'heap': 0.16; 'wrote:': 0.18; 'work,': 0.20; 'memory': 0.22; 'cc:addr:python.org': 0.22; 'cc:2**0': 0.24; "i've": 0.25; 'header:In-Reply-To:1': 0.27; "doesn't": 0.30; 'said,': 0.30; 'message-id:@mail.gmail.com': 0.30; "i'm": 0.30; 'usually': 0.31; 'stuff': 0.32; 'running': 0.33; 'fri,': 0.33; "can't": 0.35; 'objects': 0.35; 'but': 0.35; 'received:google.com': 0.35; 'subject:?': 0.36; 'pm,': 0.38; 'does': 0.39; 'subject:" ': 0.39; 'sure': 0.39; 'entire': 0.61; 'places': 0.64; 'therefore,': 0.64; 'subject': 0.69; 'fact,': 0.69; "everything's": 0.84; 'permanently.': 0.84; 'pike': 0.84; 'subject:High': 0.84; 'technique.': 0.84; 'to:none': 0.92; 'suffering': 0.93; 'serious': 0.97
DKIM-Signature v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:cc :content-type; bh=6VnGv8QR7MFM4aB+LVyebYO5OcjtnrM1UrdhzY/qwiU=; b=RrC0VGHtYaWCc0y06Yd8hoLG5hoNhbeE8AKSZHWYwfYWUjpFcQ1txnct0C+rUe0QdQ AvSTKh/OcRLxZkBSg+sjEYn7bU+BtNEIGKXcyVuRcs2vC9+dxMvQXmGT9YJDk8XmjhJz HIJ6zLE1xbQq90wvxtn9MWrnbQdw27AKylXVzdgHIvVeFkUn4tp8sv3QLCzH92cS8d+g Gjeo7/aFu9Mv5ez2RTN9LnqJfQG5v7Qp0rMjYq8yWzyemkXTMdYvIQWRoABWUDI2kISd Nf6di+fzDAFncPL5tSId+y3pyX4vZdzepQN55p71OPuARklbztFteNiU2lnWpWu2CwRf l+Pg==
MIME-Version 1.0
X-Received by 10.43.94.7 with SMTP id bw7mr13719825icc.26.1412923969210; Thu, 09 Oct 2014 23:52:49 -0700 (PDT)
In-Reply-To <87d2a0piaq.fsf@handshake.de>
References <CANm61jc=pB7n+5kuea6bmYXTbo3hXLT8d4JZx3Yq-TBtgGrFOQ@mail.gmail.com> <mailman.14590.1412378803.18130.python-list@python.org> <7ac186c3-2dbc-4cfa-ab58-37854aeb59d1@googlegroups.com> <mailman.14647.1412613796.18130.python-list@python.org> <b5ce5cc2-3a37-49e4-aa2a-d29dd3dda972@googlegroups.com> <m16vb8$psb$1@ger.gmane.org> <87d2a0piaq.fsf@handshake.de>
Date Fri, 10 Oct 2014 17:52:49 +1100
Subject Re: "High water" Memory fragmentation still a thing?
From Chris Angelico <rosuav@gmail.com>
Cc "python-list@python.org" <python-list@python.org>
Content-Type text/plain; charset=UTF-8
X-BeenThere python-list@python.org
X-Mailman-Version 2.1.15
Precedence list
List-Id General discussion list for the Python programming language <python-list.python.org>
List-Unsubscribe <https://mail.python.org/mailman/options/python-list>, <mailto:python-list-request@python.org?subject=unsubscribe>
List-Archive <http://mail.python.org/pipermail/python-list/>
List-Post <mailto:python-list@python.org>
List-Help <mailto:python-list-request@python.org?subject=help>
List-Subscribe <https://mail.python.org/mailman/listinfo/python-list>, <mailto:python-list-request@python.org?subject=subscribe>
Newsgroups comp.lang.python
Message-ID <mailman.14740.1412923972.18130.python-list@python.org> (permalink)
Lines 17
NNTP-Posting-Host 2001:888:2000:d::a6
X-Trace 1412923972 news.xs4all.nl 2894 [2001:888:2000:d::a6]:41895
X-Complaints-To abuse@xs4all.nl
Xref csiph.com comp.lang.python:78927

Show key headers only | View raw


On Fri, Oct 10, 2014 at 5:09 PM, dieter <dieter@handshake.de> wrote:
> Python does not use memory compaction but places many objects on the
> heap and therefore, long running processes
> usually are subject to memory fragmentation. As a consequence, those
> processes need to be restarted from time to time.

Pike doesn't use memory compaction either, and also places pretty much
everything on the heap. Yet its processes don't need to be restarted;
in fact, everything's designed around keeping stuff running
permanently. As Emile said, it's not a requirement, it's a
compensation technique. I've yet to build a Python process that runs
for an entire year (as I'm not confident that I can get it so right
that I don't need to update any code), so I can't say for sure that it
would work, but I do have Python processes running for multiple months
without suffering serious fragmentation.

ChrisA

Back to comp.lang.python | Previous | Next — Previous in thread | Find similar | Unroll thread


Thread

Re: "High water" Memory fragmentation still a thing? Chris Angelico <rosuav@gmail.com> - 2014-10-04 09:26 +1000
  Re: "High water" Memory fragmentation still a thing? Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2014-10-04 11:02 +1000
    Re: "High water" Memory fragmentation still a thing? Chris Angelico <rosuav@gmail.com> - 2014-10-04 12:22 +1000
      Re: "High water" Memory fragmentation still a thing? Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2014-10-04 15:48 +1000
        Re: "High water" Memory fragmentation still a thing? Chris Angelico <rosuav@gmail.com> - 2014-10-04 15:57 +1000
        Re: "High water" Memory fragmentation still a thing? Sturla Molden <sturla.molden@gmail.com> - 2014-10-04 17:51 +0000
    Re: "High water" Memory fragmentation still a thing? Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2014-10-04 16:20 -0400
    Re: "High water" Memory fragmentation still a thing? mm0fmf <none@mailinator.com> - 2014-10-05 20:23 +0100
      Re: "High water" Memory fragmentation still a thing? Steven D'Aprano <steve@pearwood.info> - 2014-10-06 07:20 +0000
  Re: "High water" Memory fragmentation still a thing? bryanjugglercryptographer@yahoo.com - 2014-10-06 09:21 -0700
    Re: "High water" Memory fragmentation still a thing? Chris Angelico <rosuav@gmail.com> - 2014-10-07 03:43 +1100
      Re: "High water" Memory fragmentation still a thing? bryanjugglercryptographer@yahoo.com - 2014-10-08 10:28 -0700
        Re: "High water" Memory fragmentation still a thing? Emile van Sebille <emile@fenx.com> - 2014-10-09 14:39 -0700
        Re: "High water" Memory fragmentation still a thing? Chris Angelico <rosuav@gmail.com> - 2014-10-10 08:42 +1100
        Re: "High water" Memory fragmentation still a thing? dieter <dieter@handshake.de> - 2014-10-10 08:09 +0200
        Re: "High water" Memory fragmentation still a thing? Chris Angelico <rosuav@gmail.com> - 2014-10-10 17:52 +1100

csiph-web