Once a week we run a mailout to our clients over night. The entire process is split over 2 tasks. One task matches clients to the products matching their criteria and puts it in a db table. The second task gets all those id's and retreives all the data for both client and product, then puts the info into an email and sends it.
Our jrun4 and mx7 instance was having troubles with the set up part a week or so ago and I increased our JVM heap to 1GB (on a 2.5 GB RAM machine). This solved the issue no problems, and now it completes the entire first stage. This is set to run for a max of 4 hours. We then schedule the second part to start 4.5 hours after the first. Even now with 1GB heap the second part is hitting20% complete and dying from an out of memory. Because its run at midnight - 4am, I cant run metrics on it (coz I am in a sleepy place) so I dont know quite whats happening to GC but I am a bit miffed it blows up. Ideas: The code is FB and straight procedural - would I be able to recycle memory better with a CFC or 2? Could my JVM be better tuned? Anything I can do to slim down memory usage or tune JVM better? Thanks. -- Duncan I Loxton www.sixfive.co.uk [EMAIL PROTECTED] --- You are currently subscribed to cfaussie as: [email protected] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
