Hi Charles -
It is not at all unusual for application users (Tableau Server or any webapp, actually) to experience latency issues when they live "far away" from the machine doing the work for them. Physical distance is not the issue as much as the time (latency) it takes to move bits from the North America to Asia over a corporate network which probably has a "small pipe" between the two continents. Those dedicated trans-con "pipes" are expensive for a company, so they typically can't handle the same "load" as the network in your office.
A standard design pattern that companies use to deal with this is to setup distinct Tableau Servers in each region, and then sync a limited amount of content between them using a third party mechanism. This is how WE deploy our big internal Tableau Server infrastructure here at Tableau, too. We call the system "ALPO". There is a very large cluster in North America, with relatively smaller servers in EMEA and London. Matt Coles can tell you more about the system if you want.
Thanks a lot for your answer.
Could you please explain/give examples of when/how you sync content between the servers? Could be it, for example, to just run TABCMD jobs that download dashboards on one server and then publish it on the other?
I am definitely interested in getting as much information as possible on this. We're getting new server core licenses soon. I need to determine if we want to put them all in the same server or if we would get better performance by having a server in EMEA.
How do I attract Matt Coles to this thread?
Tabcmd is one way, a free tool called TabMigrate is another. You can also write code which leverages our REST API to do this work, too.