From: Brandon Casci Date: 2007-01-14T03:31:23+09:00 Subject: Re: Memory Leak Madness Thanks again for all the help. My problems are gone. I still haven't tried fastthread but that's next on my list. Here is what I did: -paid a little more attention nil-ing/.clearing arrays and hashes I no longer need -traded most threads for forking (with win32-process) -queued all work in reliable-msg rather than an in memory array to-do: -swap all remaining native ruby threads with fastthreads for a little performance boost. My application uses a lot more RAM because of forking, but I've gained speed and scalability with forks and reliable-msg. I can fork more processes as needed and spread them out over many computers. The only thing I can't figure out is how to expose the reliable-msg server to outside IP addresses (it only binds to localhost) but I'll do more reading. -- Posted via http://www.ruby-forum.com/.