John, I would ditch using ns_getform and roll your own instead. What you seem to have proven is that you can upload large files with AOLserver 4.5 and the overflow goes to disk.
The question remains: how to deal with the data on disk? [ns_conn files] gives you offsets, how do you copy that data somewhere else without bloating memory? Maybe [ns_conn copy] is the problem. If it loads $len bytes into memory before it writes a file, that will bloat the memory. You might verify that this isn't a memory leak, but rather a high water mark on memory usage. Do two identical uploads, or three continue to increase memory usage, or does it stop growing? If it keeps growing, that could indicate some mem leak bug. tom jackson On Mon, Nov 23, 2009 at 6:18 PM, John Buckman <j...@bookmooch.com> wrote: > Tom, thanks for the help! > > Setting maxinput as per: > >> ns_section "ns/server/$server1/module/nssock" >> ns_param maxinput 1024 > > does indeed avoid memory bloat during the large file upload. I used your > safer ns_getform: it works fine, > > However, your ns_getform causes the nsd process to grow to the size of the > uploaded file. > > I can't figure out what it is in your code that uses lots of memory. Any idea? > > -john > > > -- > AOLserver - http://www.aolserver.com/ > > To Remove yourself from this list, simply send an email to > <lists...@listserv.aol.com> with the > body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: > field of your email blank. > -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <lists...@listserv.aol.com> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.