Wonder if you're NSV arrays are growing unbounded? How big is your nsv array getting? Do you enforce any cleanup or size limits? One potential downside of using NSV arrays is that their growth is unbounded.
Suggest you instead use the Ns_Cache() API which allows you to create either a size or time based cache. Unfortuneatly we haven't yet exposed the C API in Tcl, but I do believe there are other external cache modules available for AOLserver which can be used. - Nathan Brad Chick wrote on 10/13/03, 10:48 AM: > I'm running aolserver 4.0b10 on debian to respond to a high demand of > queries for the Chicago Marathon. I'm using the nsv arrays to keep the > data > and relevant html in memory such that I don't have to go to a db or > disk in > order to satisfy the request. > > When aolserver starts, we load the data into the arrays once from disk. > > Unfortunately, after running for some time, aolserver writes: > > unable to realloc 88435498 bytes > > to the log file (or some number) and hangs. This is consistent behavior > across all 4 machines that are running this set up. > > Any help would be greatly appreciated. -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
