I'm not much of a Server Admin....but the people who contribute on the Server Admin Community are!
I would suggest asking this question over there, as you will probably have a better chance of getting a detailed answer.
Thanks for pointing to right direction.
2 of 2 people found this helpful
I don't concern myself too much with tabrepo (I think has something to do with connecting internally to PG) or tabspawn (internally spawns new processes such as the postgres). tabprotosrv I believe is the main communicator to the source database. It typically doesn't take up much CPU, but sometimes I do have to have a look at the logs for this one when there are problems with disconnections for whatever reason to our DW.
Hi Tody Erkson,
Thanks for the reply.
We don't have any issue as of now. As each process is occupying some amount of memory so I am curios to know about them. Not sure if ,my questions are making sense but hoping to gain some knowledge on them.
- When will we see multiple instances of each of these process?
- When multiple instances are created, how much memory is allocated to each processes ? Is there any threshold limit of memory allocation to these processes?
- Is there any configuration to limit these processes?
- Are these processes always stay as it is or closed at any time, if yes when?
These things help me in understanding the RAM usage and while monitoring Memory usage.
memory is cheap, if you are running anywhere in the neighborhood of "high", then up it. these processes are anklebiters and are not so controllable as an admin.
We (Conversant) are running 256 gig of memory on each box, granted this is excessive, but it wasn't really expensive and we don't really have to worry about paging or out of memory errors.
I can't answer any of your questions and the only qualified people who could are the Tableau engineers themselves. I'm happy that I don't have to worry about knowing any of that stuff, that's what makes Tableau so nice. Honestly, trying to understand those processes and why is unnecessary busy work that most likely won't help you at all; using the recommendations set by Tableau is a far better use of your time. A broad guideline for starting out is 8GB per core and naturally this will change according to the unique demands of your reporting environment.
6 of 6 people found this helpful
Tabprotosrv.exe: Interfaces between Tableau Server and database drivers, it is essentially the lowest level of interface between Tableau and the driver. It is used by Tableau for connecting to all supported data sources. It runs while refreshes are occurring and Tableau Server is connecting to the external databases.
Tabspawn.exe: Waps most services; starts and stops services as needed. For example, if one vizql process goes down, tabspawn.exe will attempt to spin up another one.
Tabspawnde.exe: Start up service for initiating TDE requests.
Tabrepo.exe: This belongs to SOLR or Tableau Server's "search index."