A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from http://mail.python.org/pipermail/python-dev/2002-April/023715.html below:

[Python-Dev] CHUNKSIZE

[Python-Dev] CHUNKSIZE [Python-Dev] CHUNKSIZEMichael Gilfix mgilfix@eecs.tufts.edu
Sat, 27 Apr 2002 13:12:13 -0400
  This comment is more of a question.. Does the chunksize not have
to do with how the filesystem stores blocks? I *think* it's better
to retrieve in blocks that best match the size of the filesystem. So
8K would make sense since many FS's have 4K chunks and many have 16K
chunks, etc... I'm probably totally wrong so someone please tell
me why :)

On Sat, Apr 27 @ 10:07, Paul Prescod wrote:
> xreadlines' default CHUNKSIZE is 8K. minidom defaults to double that.
> 
> Have those values been keeping up with machine RAM inflation and should
> they? I presume others have thought this through but my probably-naive
> impression is that getting data in such little bytes is a waste of time
> on machines with tens or hundreds of megabytes of RAM.

-- 
Michael Gilfix
mgilfix@eecs.tufts.edu

For my gpg public key:
http://www.eecs.tufts.edu/~mgilfix/contact.html




RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4