...and the other question is whether additional backgrounders will help or potentially hurt you. Have you tested this before you invest too much time? If your CPU is already pretty high on the BG machine, then the answer may not be "more backgrounders" but "more Tableau"...Just sayin'
Thanks Jeff and Russell.
My idea is to have more backgrounders available during night time as there is no interactions traffic that time and lower number during business hours to get as much jobs funneled as possible.
We are working on getting more Tableau cores power but that is subject to more funding which will require some time so looking for interim options.
In other thread I didn't yet understand having 2 tabcmd threshold settings if they both serve same purpose.
Get Outlook for Android<https://aka.ms/ghei36>
I think the main thing here is to understand whether you can actually increase throughput with more backgrounders on the same machine - sometimes you can, but if the machine is already "too busy" with the existing backgrounders, then adding more won't help you.
If you aren't actually refreshing extracts during the day at all, then it probably wouldn't hurt (aside from wasting some RAM on processes not doing work for you) to have these running ALL the time. Again, you'd probably want to test
Just curious, can we change # of Backgrounder instances using any command line (I couldn't find this option in tabadmin or tabcmd) - I am ok with restarting the machine as well.
1 of 1 people found this helpful
"I'm willing to take some risk and realize that these techniques are not supported and that I can't 'call for help' if I get into trouble" answer:
I'd read the ENTIRE article below (it's long, but awesome) and then decide whether you want to try this stuff for yourself and whether you feel comfortable risking the health of your server doing so. Again, this stuff is not supported
PRIMARY ADJUSTMENTS - WORKER0
Unlike the UI, your changes here will just be applied, you may not get an error or warning if you misconfigure (like forget to add a Data Engine or File Store somewhere).
- VizQL: worker0.vizqlserver.procs #
- Application Server: worker0.vizportal.procs #
- Background Server: worker0.backgrounder.procs #
- Cache Server: worker0.cacheserver.procs #
- Data Server: worker0.dataserver.procs #
- Data Engine: worker0.dataengine.procs #
- File Store: worker0.filestore.enabled true/false
- Repository: pgsql0.host Machine Name of Primary
- Search and Browse: worker0.searchserver.procs 1
- Gateway: worker0.gateway.enabled true/false
WORKERS - WORKER1 -> WORKERN
- Add a Worker: worker.hosts “Primary, IP1, IP2”
- workerN.XXX.procs [just replace worker0 with workerN]
- If you want to run a repository on another host: pgsql1.host IP address of worker
- If you have more than one pgsql repository: pgsql.preferred_host MACHINE NAME
this is really excellent article and too technical; seems little advance to me.... I am wondering what would be steps to Dynamically Increase and Decrease "# Backgrounder processes" on Tableau 9.0 server to dynamically balance the server load.
I message the publisher on that article to see if he can help.
Well, it is technical, because you're "working around" the designed behavior of the software.
If your requirements are "Easily dynamically increase / decrease the # of backgrounders", then the answer is "No, there is no way to do this".
Thanks Russel. My requirements are not to “Easily” change # backgrounders… I am ok with complexity. But in that article couldn’t figure steps or some sample script to try out in dev environment. This will help us big time until we upgrade our infra next year.
Hi Tamas, I read in that Blog that you're working on "How to implement" this piece on this.... really curious if this is something you can help with?