topic Re: Dashboard Best Practices & Performance in Dashboards & Visualizations

Dashboard Best Practices & Performance

subtrakt — Sat, 08 Mar 2014 14:05:09 GMT

Hello,
I have a dashboard that displays around 30 saved searches. I have it set to load all the saved searches when the dashboard is loaded and refresh every 600 seconds - performance is fair.

To increase performance, I'm debating on scheduling the saved searches but don't want to create too much overhead when the dashboard is not in use. Would using dashboard inline searches be a better option?

Thanks!

Re: Dashboard Best Practices & Performance

martin_mueller — Sat, 08 Mar 2014 15:17:11 GMT

Inline or saved searches don't affect their performance, that's just where the search string is stored.

Some common ways to improve performance of a many-searches dashboard:

Look for commonality between searches. When found, combine several searches into one and use post-processing to drive several panels off one search.
Look for searches eligible for report acceleration
Look for long-running searches left over after these steps and schedule those searches

Above all that there's general search performance optimization, such as reducing the number of events scanned to achieve the search goal or replacing costly operations with cheaper ones or avoiding inefficient wildcard matches.

Re: Dashboard Best Practices & Performance

a212830 — Sat, 08 Mar 2014 16:25:25 GMT

Is there doc on how to handle post-processing?

Re: Dashboard Best Practices & Performance

martin_mueller — Sat, 08 Mar 2014 16:44:27 GMT

Sure: http://docs.splunk.com/Documentation/Splunk/6.0.2/AdvancedDev/PostProcess