John E. Mayorga [[EMAIL PROTECTED]] writes:
> I believe it is actually about 100 bytes per file, plus a little
> overhead. This was suggested earlier on this list. I verified the
> information with a 35 Gig mailstore sync, after doing a "find . | wc
> -l" to count the number of files and directories rsync was to sync.
There should be a note from me to this list back in the January
timeframe where I tried to summarize some details on this - one thing
that's important to note is that the filelist memory grows
exponentially, so it's not a linear "n bytes per file" sort of thing,
and if you have enough files, you may be using twice the memory than
under other conditions.
But in terms of space usage under NT, Martin's original point should
be accurate - the allocations are just normal C RTL allocations, so
they're just simple memory usage under NT, which it will take from
RAM/paging just like any other memory user in the system. How much
physical memory is actually allocated is outside of rsync's control.
I'm not personally aware of any settings under NT that would make it
avoid allocation physical memory, and in fact I believe that other
than for executables (which can swap directly to the source file), all
other memory is automatically backed in the paging system at
allocation time.
-- David
/-----------------------------------------------------------------------\
\ David Bolen \ E-mail: [EMAIL PROTECTED] /
| FitLinxx, Inc. \ Phone: (203) 708-5192 |
/ 860 Canal Street, Stamford, CT 06902 \ Fax: (203) 316-5150 \
\-----------------------------------------------------------------------/
