What kind of saved searches are you performing? If they're mostly of using a time chart for a count, you're halfway there. Look into summary indexing if you haven't already: http://docs.splunk.com/Documentation/Splunk/6.0/Knowledge/Usesummaryindexing
See if any of the listed use cases apply to yours.
Definitely check out this if you haven't already:
http://docs.splunk.com/Documentation/Splunk/6.0/AdvancedDev/PostProcess
I'd consider a few other things (mainly taken from the above two references) if you wanted to cobble all these requirements together:
- How related are these searches? Are they for the most part collecting from the same type of logs?
- How expensive is each search? Is the purpose of this dashboard to summarize?
- Do they need to be ad-hoc or real-time? Can you live with hourly updates if they truly are high volume searches/results?
- How much data did you really want to consume out of this dashboard?
- And finally/most importantly: is summary indexing ok?
If you can combine a lot of your requirements and using a base search, I think you should be able to achieve the rest. If you want to persist your scheduled searches, I'd recommend summary indexing and using adapted queries in this dashboard to just aggregate from there. Some overhead, but most efficient in the end potentially.
