[EDIT] --- I've updated my approach in a comment below using Symbolic Links instead.
Just a tip for anyone interested.
I've come to realize two things:
- my local Log folders were really big (combined ~400MBs) -- fairly fresh OS and install of latest versions
- they aren't useful unless troubleshooting
- I was burning ~8-9 GBs of upload daily while working with Tableau Desktop/Prep .... yes, GigaBytes. And my network was always kind of laggy due to this.
I have both OneDrive and Google Backup & Sync installed. Thus, with the logs located where they are both of these tools were backing up the log/txt files every time Tableau touched them. Most files were 3-4 MBs, but one (Desktop) was 200MBs and was touched continuously daily. I've since purged the logs (keeping just the empty CrashDumps folder) and everything is fine. But now my PC is oddly more responsive online because 100% of the UL isn't being consumed by log backups all day long.
Anyway. Just a tip in case others are in a similar boat.
Check your repository\log folders as they may too be really big and constantly backed up either by something similar, or just a corporate solution you aren't aware of. Either way, it's "wasted" bandwidth as is.
What have I done to stay on top of it?
- found both log folders (Desktop & Prep are discrete)
- created a PowerShell script (c:\purge-tableau-logs.ps1):
Remove-Item -path 'C:\Users\UserFolder\OneDrive\Documents\My Tableau Repository\Logs\*' -Include *.txt, *.log
Remove-Item -path 'C:\Users\UserFolder\OneDrive\Documents\My Tableau Prep Repository\Logs\*' -Include *.txt, *.log
# notes: don't use $Env:userprofile as this script may run as the System-User
# : remove the \OneDrive\ if you don't use OneDrive
# : change \UserFolder\ to your user folder
- setup shutdown trigger for the script in my GPEdit.msc > Computer Configuration > Windows Settings > Scripts. I used a 'shutdown' (instead of login/logoff) script so the files won't be there on a fresh-boot (with background backups). Or use the User-Config version for a login/logoff trigger instead of a reboot trigger. Whatever suits your needs.
* note: I did have to enable script execution in PowerShell with : set-executionpolicy remotesigned : via PowerShell as Admin.
Now. Just rebooting will purge my logs, but they'll hang out and stay small-ish during the day if I need to submit them for assessment.
If you have a more elegant solution. I'm happy to hear it. I looked inside Desktop and couldn't find any log-control so I just made my own solution instead.
Message was edited by: Michael Lowden. to add a better solution in the comments