I also run a front end for this app via a webpage that I host on my apache web server on the same machine so I was worried about the resources left over to handle any http queries. In the end I rewrote the app to implement some load balancing and had the app respawn itself after ((scalar(@servers)/5)+1) and then start from where it left off. At first I tried system() but this of course did not work due to the blocking nature of system wating for a return so I used exec() to overwrite the current pid and dump the resources back to the OS. Seems to be working out nicely and each iteration only uses about 20% of the memory now.
In reply to Re^4: release threads resources?
by Elijah
in thread release threads resources?
by Elijah
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |