1 of 1 people found this helpful
Hey Jeff -
I'm not an expert on Online's architecture, but I thinkyou've actually pretty much answered the question yourself in the final sentence of your question. As you know, much of our caching activity happens at the level of the individual VizQL Server process - which is why you might lower the number of processes available in order to avoid artificially driving down your cache hit ratio. Since we don't share cache across vizqls, you don't want more than you need running based on user load.
Online is a different story - it needs to scale all the time so has many more vizqls running. Therefore the chance that "user2" happens to hit the same vizql as "user1" did (and using cache) is less. I'm pretty sure that "your" site doesn't have vizqls associated that ONLY do work for your site....
Thanks Russell. I also got some advice from Michael Kovner, who let me know that if two people are logged in at the same time, they will share a session, and therefore a cache. Now I just have to find a way to prime the cache, or trick Tableau Online into thinking that a User is logged into the 1st view. Any idea on how to do this? (a trained monkey is my current option)
Mike is my buddy —
Absolutely true in the “Corporate” version of Tableau Server – neither of us know for sure if this is true for Online/Public, as well – so keep that in mind. He was talking about shared sessions, where we share a single session across multiple users as long as no one changes / touches the viz. The second someone filters or modifies something…new sessions.
Maybe you could do this with some sort of a browser macro?