RE: memory requirements was RE: out of memory in build_hash_table

Granzow, Doug (NCI) [[EMAIL PROTECTED]] writes: > From what I've observed by running top while rsync is running, its memory > usage appears to grow gradually, not exponentially. The exponential portion of the growth is up front when rsync gathers the file listing (it starts with room for 1000 fi

Re: memory requirements was RE: out of memory in build_hash_table

"Granzow, Doug (NCI)" wrote: > > From what I've observed by running top while rsync is running, its memory > usage appears to grow gradually, not exponentially. A rsync may take > several hours to complete. (I have one running now that started over four > hours ago. The filesystem contains 236

RE: memory requirements was RE: out of memory in build_hash_table

Well, for reference, here's what I'm running: The mirror is running Solaris 8, the source is running Solaris 7. Both are running the same version of rsync: rsync version 2.5.4 protocol version 26 Copyright (C) 1996-2002 by Andrew Tridgell and others Capabilities: 64-

RE: memory requirements was RE: out of memory in build_hash_table

Granzow, Doug (NCI) [[EMAIL PROTECTED]] writes: > Hmm... I have a filesystem that contains 3,098,119 files. That's > 3,098,119 * 56 bytes or 173,494,664 bytes (about 165 MB). Allowing > for the exponential resizing we end up with space for 4,096,000 > files * 56 bytes = 218 MB. But 'top' tells

memory requirements was RE: out of memory in build_hash_table

>The key growth factor for the file construction is going to be >per-file information that's about 56 bytes (last I looked) per file. >However, the kicker is that the file storage block gets resized >exponentially as you have more files. So for 385,000 files it'll >actually be a 512,000 file bloc