Hello,
I have been running tabjolt on my test Tableau environment where I am the only one authorized user. The machine is 4 core VM with 24 GB memory with one of each type of Tableau processes running. All the configuration settings are out of the box, no customizations.
I have built a very simple workbook to start with. It has just a single 4 bar chart in one sheet, which is used in one dashboard. The data source for the workbook is the Superstore sample data shipped with the Tableau desktop. I run the following command go --t=testplans\InteractVizLoadTest.jmx --d=1200 --c=1, which means one concurrent user for 20 minutes. Again, I am the only one with access to this environment, so there is no load other than tabjolt.
I am getting pretty consistent results as follows.
After about 100 seconds, all bootstrap requests start to fail with 100%. The error is "Timer did not end properly. SubResult EndTime is 0.".
Memory and CPU are not the bottleneck
If I browse to the server in my browser on my laptop ( different from tabjolt running machine), I am not able to open this report, it spins a wait cursor for a long time and then shows an error. Other reports open ok. When the system goes in this state I will no longer be able to run this report unless I restart Tableau services ( or at least kill vzqlserver.exe from the Task Manager ).
Even if I leave it for an hour and all the sessions should presumably expire when I am back - this report can no longer be opened.
I used jstack to create a callstack of vzqlserver when it gets in this state and out of 237 threads - 188 are in the
WAITING (parking) state. I don't know enough java to tell what is it waiting for.
So the question is, what is the limiting factor here? How can I tell? 100 seconds by one concurrent user does not seem like a huge load to me. I am ok on CPU and memory, yet, this report can no longer be viewed from any client unless I bounce vzqlserver.exe process.
Thank you,
Tatiana
I think we've solved it: The workbook in question was a nice, simple test intended just to exercise Tabjolt. The datasource was an Excel worksheet. The datasource was not extracted. Once we extracted and re-published, the Tabjolt tests ran flawlessly. My theory here is that the operating system was having a difficult time opening multiple connections to the Excel datasource. Once we changed the datasource to something designed to handle multiple simultaneous client requests (a TDE in this case), our problems went away.
