On Premiss Server Slowing Down - SQL Log files ?

Hi Thibaut,

1. The purpose of the Tracker is explained here: https://support.sugarcrm.com/Knowledge_Base/Reports/Understanding_Tracker_Reports/index.html 

2. The Tracker usage is configurable via Administration (navigate Administration -> Tracker)
It looks like this:

3. If Tracker is enabled, it can collect A LOT of data. For such case, there is out-of-the-box Job that does clear the table regularly

I'd suggest checking whether Job is Active and actually run 

If the Job is active and running regularly, the Tracker itself may contain important information useful for finding the performance bottle-neck and that is from what performance optimization starts.
What performance optimization usually includes you can read here: SugarCRM Performance Tuning. Optimize Your CRM System | Integros 

If you have any questions feel free to reach out to me dch@integroscrm.com 

All the best,

Dmytro Chupylka

Hello Dmytro, 

Thank you for your advise. We've set up some trackers few months ago and the amount of data collected is huge. 

there's a scheduler meant to delete the tracker file but it doesn't seems to be running ? 

Can the accumulation of files be responsible of the CRM loss of speed ? 

Regards 

Hi Thibaut,

function::trimTracker is that job that should clear the Tracker tables from the data older specified in the Tracker configuration (the parameter is in Administration -> Tracker)

However, "Job log" provided on your screen is empty an Last Successful Run is "Never", seems this Job haven't been working ever.... You could check whether other active jobs have any successful runs.
If there are issues with them as well, try to check the "cron" on your server, maybe it is not configured properly preventing Jobs to run

All the files uploaded are represented in db with referrals, so in case of many files, the poor or inappropriate indexing potentially may affect database data reading performance.
But that is guessing, if you check the link to performance tuning suggested above, you will find a lot of potential reasons for performance downgrade and involving experts saves time and nerves.

Prior to checking the cron and clearing the Tracker (clearing db and reindexing definitely may help), I'd suggest making a backup of the db just in case that clearing Tracker won't help and you decide to involve experts, because the Tracker may contain information that can speed up search for performance bottle-necks

All the best, 

Dmytro

Hello, 

Just in case someone reads this discussion while being in trouble with his data base, if found the tables and the fixing commands to get rid of these over sized tables, 

1st command :  mysql -u [user] - p 

2nd command : use [database];

3nd Command : 

SELECT        table_name AS `Table`,      round(((data_length + index_length) / 1024 / 1024), 2) `Size in MB`  FROM information_schema.TABLES  WHERE table_schema = "[database]" ORDER BY `Size in MB`;

4th Command : to truncate the over sized  table, 

truncate [table names];

I got rid of  "tracker" and "activities" 

don't forget to replace the data base and user name in the commands. 

Thank you for reading 

Thibaut, did truncation fix the slowdown observed?

Hello, 

Yes, is has fortunately. 

I hope this chat will help someone who's facing this situation later on.