Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #10717 > unrolled thread
| Started by | Thomas Jollans <t@jollybox.de> |
|---|---|
| First post | 2011-08-02 13:09 +0200 |
| Last post | 2011-08-02 13:09 +0200 |
| Articles | 1 — 1 participant |
Back to article view | Back to comp.lang.python
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: python reading file memory cost Thomas Jollans <t@jollybox.de> - 2011-08-02 13:09 +0200
| From | Thomas Jollans <t@jollybox.de> |
|---|---|
| Date | 2011-08-02 13:09 +0200 |
| Subject | Re: python reading file memory cost |
| Message-ID | <mailman.1762.1312283392.1164.python-list@python.org> |
On 02/08/11 13:00, 张彤 wrote: > Thanks Peter! Your explanation is great! > And one more question: > Why it is still keeping the memory even when I del the large array in > interactive python mode? This is an optimisation of the way the Python interpreter allocates memory: it holds on to memory it's not using any more for a while so it can be easily re-used for new objects --- this is more efficient than giving the memory back to the operating system only to request it again shortly afterwards. > > -----Original Message----- > From: Peter Otten [mailto:__peter__@web.de] > Sent: Tuesday, August 02, 2011 4:26 PM > To: python-list@python.org > Subject: Re: python reading file memory cost > > Chris Rebert wrote: > >>> The running result was that read a 500M file consume almost 2GB RAM, >>> I cannot figure it out, somebody help! >> >> If you could store the floats themselves, rather than their string >> representations, that would be more space-efficient. You could then >> also use the `array` module, which is more space-efficient than lists >> (http://docs.python.org/library/array.html ). Numpy would also be >> worth investigating since multidimensional arrays are involved. >> >> The next obvious question would then be: do you /really/ need /all/ of >> the data in memory at once? > > This is what you (OP) should think about really hard before resorting to the > optimizations mentioned above. Perhaps you can explain what you are doing > with the data once you've loaded it into memory? > >> Also, just so you're aware: >> http://docs.python.org/library/sys.html#sys.getsizeof > > To give you an idea how memory usage explodes: > >>>> line = "1.23 4.56 7.89 0.12\n" >>>> len(line) # size in the file > 20 >>>> sys.getsizeof(line) > 60 >>>> formatted = ["%2.6E" % float(x) for x in line.split()] >>>> sys.getsizeof(formatted) + sum(sys.getsizeof(s) for s in formatted) > 312 > > > >
Back to top | Article view | comp.lang.python
csiph-web