Thanks for the quick response. I have looked at that article.

My server is configured to allow 256MB and 10 minutes of processing. The database only has roughly 40 days of data in it. We average 700 visitors per week. So, if this is a scalability issue, I believe the issue lies in the initial database foundation of the component. We had over 6 months of data in the 1.0 version of this component previously and it still provided reports and PDFs but just took a lot of process time.

I will try increasing memory and script time again to see if I get better results. However, I highly recommend streamlining these processes as much as possible. Many sites are looking to this component for historical data and reports that cannot be acquired anywhere else. You have a hot product here. I think it just needs to be made more efficient.