VizAlerts performance issues after upgrading Tableau Server to 2021.4

[FSMA-au]

Performance of VizAalerts has degraded significantly after we upgraded from Tableau Server 2020.4 to 2021.4. We have log files that show that visualisations now take almost twice as long to run in VizAalerts as they did previously. This is impacting significantly on our ability to deliver visualisations to this business in a timely manner each morning.

Just wondering if anyone else has encountered and/or resolved this issue?

Cheers.

[mcoles]

Hi!

I'm not aware of any reason to expect such a degradation. Problems like this typically have nothing to do with VizAlerts, and are either an issue with Tableau Server, back-end databases, drivers, or sometimes (but rarely in my experience) networking. Some questions to help narrow down where the problem is.... :

Do the vizzes you are sending use live connections to a database, or are they based on extracts? Do they connect through published data sources? Have you noticed any other performance issues with vizzes rendered in-browser by users (ideally this would be based on performance data you are monitoring).

[jdrummey]

I haven't encountered this either. My first thought would be to debug by logging into Tableau Server in a web browser and loading up the slow trigger views or content reference views...if the views are also slow to render in the web browser then you can rule out VizAlerts and start digging into everything Matt mentioned.

[FSMA-au]

Hi Matt - thanks for the reply.

The vizzes in question are connecting to a published live data source (to an Oracle database view). Most of our vizzes normally do use extracts - however these vizzes run very early in the morning - before the extracts have completed, so we use a live datasource instead for these.

Initially we assumed the issue was poor Tableau performance - however we have not seen a noticeable degradation in interactive performance.

Comparing the VizAlert log files from before and after the upgrade shows that the same vizzes are taking approx. twice the time they took previously. For example, a pdf viz in VizAlert that ran in 1min 30 sec before is now running in 2min 50 sec.

Quite clearly these are slow vizzes in the first place - but this is because they are using a large live datasource. The original performance wasn't an issue because no-one uses these vizzes interactively - they are only run using VizAlerts.

Your reply prompted me to consider if I can reduce the size of the datasource - to see if this improves performance. The datasource contains data for approx. 4 years - however the dashboards we are using it for only ever show current year and previous year, so I am going to add a filter to the Oracle database view to limit the data to 2 years and see if this reduces the run time for these vizzes.

Thanks again for your assistance.

Cheers, Darran

Darran Ambrose Business Intelligence Manager National Pharmacies I National Support Office 52 Gawler Place, Adelaide SA 5000 T - 08 8223 0328 M - 0411 484 213 E - @.**@.> www.nationalpharmacies.com.auhttp://www.nationalpharmacies.com.au/ @.***

From: Matt @.> Sent: Wednesday, 12 January 2022 5:17 PM To: tableau/VizAlerts @.> Cc: Darran Ambrose @.>; Author @.> Subject: Re: [tableau/VizAlerts] VizAlerts performance issues after upgrading Tableau Server to 2021.4 (Issue #192)

Hi!

I'm not aware of any reason to expect such a degradation. Problems like this typically have nothing to do with VizAlerts, and are either an issue with Tableau Server, back-end databases, drivers, or sometimes (but rarely in my experience) networking. Some questions to help narrow down where the problem is.... :

Do the vizzes you are sending use live connections to a database, or are they based on extracts? Do they connect through published data sources? Have you noticed any other performance issues with vizzes rendered in-browser by users (ideally this would be based on performance data you are monitoring).

- Reply to this email directly, view it on GitHubhttps://aus01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Ftableau%2FVizAlerts%2Fissues%2F192%23issuecomment-1010693443&data=04%7C01%7Cdambrose%40fsma.com.au%7Cbbb1527af16f494bd91a08d9d59766b4%7C7fb748f99bc34238a3b324d67876d616%7C0%7C0%7C637775668509124875%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=hZ6gKvERmE6yOjhaLM0R7WUD3BgH6z30JY3NTZaU9iQ%3D&reserved=0, or unsubscribehttps://aus01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAXIM5KY536OXJ7D6TR55VR3UVUPXXANCNFSM5LXX2XCA&data=04%7C01%7Cdambrose%40fsma.com.au%7Cbbb1527af16f494bd91a08d9d59766b4%7C7fb748f99bc34238a3b324d67876d616%7C0%7C0%7C637775668509124875%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=d8xh7zQrYgksaQlwiOn839plTUHPd8Qm5KPP5X2LeOw%3D&reserved=0. Triage notifications on the go with GitHub Mobile for iOShttps://aus01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapps.apple.com%2Fapp%2Fapple-store%2Fid1477376905%3Fct%3Dnotification-email%26mt%3D8%26pt%3D524675&data=04%7C01%7Cdambrose%40fsma.com.au%7Cbbb1527af16f494bd91a08d9d59766b4%7C7fb748f99bc34238a3b324d67876d616%7C0%7C0%7C637775668509124875%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=oTuPfeiSwWQVS6pkcJDOY%2BG9uCEiQfAgSZxx9JTc8OA%3D&reserved=0 or Androidhttps://aus01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fplay.google.com%2Fstore%2Fapps%2Fdetails%3Fid%3Dcom.github.android%26referrer%3Dutm_campaign%253Dnotification-email%2526utm_medium%253Demail%2526utm_source%253Dgithub&data=04%7C01%7Cdambrose%40fsma.com.au%7Cbbb1527af16f494bd91a08d9d59766b4%7C7fb748f99bc34238a3b324d67876d616%7C0%7C0%7C637775668509124875%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=ClxGkBjeGp0o%2FBefDxwo48lPuY%2BSqVuik8Vz5KLjiNk%3D&reserved=0. You are receiving this because you authored the thread.Message ID: @.**@.>>

** Confidentiality/Limited Liability Statement This message and any attachments to it are confidential and are intended solely for the use of the named recipient. If you are not the named recipient, you must not disclose, use or distribute the information contained in this message or any attachments to it. If you have received this message in error, please notify the sender immediately by return Email and destroy the original and any copies. Although precautions have been taken, neither the sender nor the Friendly Society Medical Association Limited warrant that this message or any attachment transmitted with it are free of viruses or any other defect. Any loss/damage incurred by opening or receiving this message or any attachments is neither the sender's responsibility nor the responsibility of the Friendly Society Medical Association Limited. Any opinion or advice expressed in this message is that of the sender and does not represent the position of Friendly Society Medical Association Limited. **