title: storing huge amount of records into classic asp cache object is SLOW
body: <p>we have some nasty legacy asp that is performing like a dog and i narrowed it down to because we are trying to store 15K+ records into the application cache object.  but that's not the killer.  before it stores it, it converts the ADO stream to XML then stores it.  this conversion of the huge record set to XML spikes the CPU and causes all kinds of havoc on users when it's happening. and unfortunately we do this XML conversion to read the cache a lot, causing site wide performance problems.</p>
  
  <p>i don't have the resources to convert everything to .net.  so that's out.  but i need to obviously use caching, but int his case the caching is hurting instead of helping.   is there a more effecient way to store this data instead of doing this xml conversion to/from every time we read/update the cache?</p>