would the residual 300+mb be the size of the query persisting in memory until the page goes out of scope? (anyone want to jump in here and explain how garbage collection works on CF?)
how about dumping it to a file (WDDX perhaps?) and then deliberately clearing the query, to see if the memory returns? just an idea barry.b -----Original Message----- From: Yorke Hinds [mailto:[EMAIL PROTECTED] Sent: Thursday, 8 April 2004 8:25 AM To: CFAussie Mailing List Subject: [cfaussie] MX Performance/Memory I have large query that processes about 10,000 records, it take a short while to process but only happens once a day. I have notices MX chews up the CPU to max at 100%, it also consumes memory from 60MB to about 360MB. Once the query has run, the CPU returns to normal but the memory usage remains over 300MB. Any ideas to improve performance --- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] MXDU2004 + Macromedia DevCon AsiaPac + Sydney, Australia http://www.mxdu.com/ + 24-25 February, 2004 --- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] MXDU2004 + Macromedia DevCon AsiaPac + Sydney, Australia http://www.mxdu.com/ + 24-25 February, 2004
