>The memory usage of the PDF report generation is defiantly a problem. >It is what we where trying to address with the usage of the thread tag. >The idea being that by splitting the process into separate threads and >throttle them down would allow the server time to clean up memory used >in previous iterations. > >That is a topic for a seperate discussion. How does <cfreport...> work >in large iterations. We found that no matter what we did, the memory >used by the report tag would just climb and climb each iteration unless >we broke up the process into completely separate HTTP requests. > >By creating a template that would process a small number of reports per >request and then send a page to the browser with a META refresh to >re-request the page in one second. This works fine.
While certainly not ideal, what if you split things up like this: 1) You create one template that creates a report based on some kind of unique key identifier. 2) You create a second template that loops through all the reports you need to create and call the first template using CFHTTP. This should at least sort of emulate the "meta refresh" technique, but allows you to automate the process w/out relying on a browser for the meta refresh. -Dan ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to date Get the Free Trial http://ad.doubleclick.net/clk;203748912;27390454;j Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:308861 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
