Loading one simple report with one user can spike the cpu.  Multiple users on that same report cause the cpu to go insane.

Global caching needs to be a thing in reporting...you guys are always looking for performance improvements anyway.

Current Scenario as defined by support:
- Person 1 hits report 1, reporting processes\renders it
- Person 2 hits report 1 (same params), reporting processes\renders it
- Person 3 hits report 1 (same params), reporting processes\renders it
...

Expected Scenario:
- Person 1 hits report 1, reporting processes\renders it, processed data result is cached
- Person 2 hits report 1 (same params), reporting retrieves the processed data from cache, and report is rendered
- Person 3 hits report 1 (same params), reporting retrieves the processed data from cache, and report is rendered
- Person 4 hits report 1 (same params), reporting retrieves the processed data from cache, and report is rendered
(10 minutes elapses, or whatever the timeout is)
- Person 5 hits report 1, reporting processes\renders it, processed data result is cached