Hi Sam, > Oh, and the relative lifetime of these objects drops significantly as > well. > the disk table is going to last for LOTS of milliseconds (10ms per I/O > at least, times too many to count). here you won't incur ANY I/O > unless paging gets involved. > so you reduce the elapsed time by orders of magnitude for these table > operations as well, if you have just 10ms of CODE to populate the in > memory table it would be a HUGE table).. > > not to mention all the I/O impact on the real table. disk arm movement, > blah blah. > (and impact on the sql system buffering, cache flushes, etc.. ) > > Sam
All this certainly sounds promising, minimizing the locks on the resources should solve the problems I've been having, very cool news indeed. Now, I'm not used to working with QofQ's at all, can you provide a little example of how I can query the in memory query and populate my real life tables with it? For instance my current queries using the temp table look something like: INSERT INTO RealTable (col1, col2, col3) SELECT Col1, Col2, Col3 FROM #TempTable How can this be reworked to draw from the in memory query opposed to the temp table? Thanks Sam, once I've got this I'll do some load testing and see how she holds up. Rob ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to date Get the Free Trial http://ad.doubleclick.net/clk;207172674;29440083;f Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:317707 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
