3 of 3 people found this helpful
Russell SEES ALL. Russell KNOWS ALL (not!). Russell has no SOCIAL LIFE (true.)
Anyway, do you feel 100% comfortable that "local" users in China are OK with dashboard performance? In other words, are you really sure the the bad performance is limited to people OUTSIDE of China?
If that is the case, the first thing that you should consider looking at is network latency between your China-based users and "rest of world". If "rest of world" users are hitting the Tableau Server in China using a "small network pipe" then things could very well be slow because there isn't a "big enough pipe" for Tableau Server to send the users what they need.
This isn't Tableau's fault, of course. It's the network. You might be able to compare results of rendering a dashboard in China vs. Elsewhere using your browser's built-in ability to monitor responses to requests across the network:
If the same requests load "fast" in China, but "slow" everywhere else, you're dealing with a network issue. The company in question needs more bandwidth OR they need to deal with network routing issues - neither of which YOU can help them with.
Another way you can take a look at this is using the "Load Time" report in Tableau Server:
Have some one in China render a viz, then render the viz outside of China. If you see the same (or lower) load time for the "outside of China" render, then you can be 100% sure that Tableau is doing it's job RENDERING the report quickly, it's just taking a long time to get the result over the network to the users.
By the way, you typically DON'T want users doing what they're doing. The server itself should be close to them.
Thank you Russell Christopher Russell The Al(mighty)
Yes local users in China do not see a performance issues, its only their team members from other countries have performance issues
Thing to note here is, in China web traffic goes through GFW ( Great Fire Wall) for some reason one great wall is not enough :-), for instance if I were to login to Tableau.com which is hosted in US, it would pass through GFW hence the overall performance is slow, but I am not sure if web traffic hitting the servers which are in China would go through GFW
I was thinking out of the box, would it help if we were to have a distributed setup of one instance of VizQL, application server and cache server outside of China, lets say either in HK or in Singapore or in South Korea which has proximity to China, would this help in anyway ?
Without additional software (Palette-software), there is no way to "force" users to one worker or another when you hit a cluster. So, it might help sometimes, but you are also just as likely to start seeing your Chinese users hitting the worker you put outside the firewall -- so now you're just moving your problem around.
Since it sounds like this is a problem they'd experience with ANY of their shared apps, have you asked them about what they do with other services that are shared between China and the outside world?
- If they have solved this issue with other apps, I'd think the same steps would work for Tableau.
- If they've never been able to solve it, then there really shouldn't be an expectation that Tableau will be any different.
- If they run distinct systems inside / outside of China, they should consider doing the same thing with Tableau.
But again, this whole discussion depends on the fact we're dealing with a Network / Firewall issue. You really should be 100% certain of that before you start making pronoucements, or you may come out looking dumb