Dashboard Performance Issue - Event & EventArchive Tables
Resolved
Hi Team,
Hope you are having a good day today.
Some of our clients have the performance issue that the dashboard is quite slow.
Those clients have more than 100 users, and Event & EventArchive tables are growing very large and every time after deleting contents from those two tables, the performance becomes better.
Our team would like to get advice about how to setup automatically truncate those two tables at a regular basis like 15 days or 20 days.
And we also want to know why those two tables will impact our dashboard performance, we have Activity Tab to monitor dashboard usage, push reports and users logins.
Thanks for your assistance.
Regards,
Nancy
The same problem 
Hi Nancy,
Thanks for reaching out. When loading Admin Console, setting up Broadcasts, and in other locations in the application, Yellowfin will search for all events within the last three months, going from the event cache to the event table to the event archive table. There is a configuration toggle in newer builds of YF to be able to set the number of days in the past to fetch events from the events table.
In staying on an older version/build however, you can still indeed improve performance by limiting the size of the Event and EventArchive tables alone. Please reference our How to Limit the Size of the Event Tables Wiki entry for two configurations available to "Archive tasks from the EVENT table, the job runs every day, searches for events older than xnumber of days ( eg. 30 days)," and "Delete records from the EVENTARCHIVE table older than x number of days ( eg. 60 days)."
Please let me know if you have any further questions.
Regards,
Mike
Hi Nancy,
Thanks for reaching out. When loading Admin Console, setting up Broadcasts, and in other locations in the application, Yellowfin will search for all events within the last three months, going from the event cache to the event table to the event archive table. There is a configuration toggle in newer builds of YF to be able to set the number of days in the past to fetch events from the events table.
In staying on an older version/build however, you can still indeed improve performance by limiting the size of the Event and EventArchive tables alone. Please reference our How to Limit the Size of the Event Tables Wiki entry for two configurations available to "Archive tasks from the EVENT table, the job runs every day, searches for events older than xnumber of days ( eg. 30 days)," and "Delete records from the EVENTARCHIVE table older than x number of days ( eg. 60 days)."
Please let me know if you have any further questions.
Regards,
Mike
Hi Nancy,
I just wanted to check in and see how things are going with this.
Regards,
Mike
Hi Nancy,
I just wanted to check in and see how things are going with this.
Regards,
Mike
Hi Nancy,
I'm going to go ahead and mark this one as Resolved since I haven't heard back from you, but if you have further questions or concerns on this, if you respond, it will re-open the case and put it back in my queue and I'll be happy to help.
Regards,
Mike
Hi Nancy,
I'm going to go ahead and mark this one as Resolved since I haven't heard back from you, but if you have further questions or concerns on this, if you respond, it will re-open the case and put it back in my queue and I'll be happy to help.
Regards,
Mike
Replies have been locked on this page!