Lots of folks understand that each VizQL process on Tableau Server has its own cache, and that Tableau Server performance is dramatically improved if one gets a cache hit when rendering a report.
So, wouldn’t it be great if we could pre-populate the cache before a user comes along?
Yes!
And since we can execute a report with TabCmd, shouldn’t we be able to warm the cache with a few executions of TabCmd getagainst the reports we want loaded in the cache?
No!
Report rendering activity initiated by TabCmd is actually carried out by the Application Server process, not VizQL.
Don’t believe me? See for yourself. Below, I’ve just executed TabCmd to render a dashboard as a PNG. Note where the action is (wgserver) and here it isn’t (vizqlserver):
