Hi Anton,
I hope you are doing good !!
<entry key='database.historyDays'>365</entry>
I have configured historyDays to 365 days, I have noticed that traccar is executing some jobs to analyze the records which are older then 365 days at 04:30 PM (UTC +05:30 Indian standard time)
At that time my database consumption reaches at its highest limit and I am getting performance issues with the system.
Can you guide me to configure same at midnight or between 1 AM to 5 AM (UTC +05:30), I mean how I can set that procedure time specific to prevent database load during pick hours ?
Any solution will be highly appreciable.
Hi Anton,
I hope you are doing good !!
I have configured historyDays to 365 days, I have noticed that traccar is executing some jobs to analyze the records which are older then 365 days at 04:30 PM (UTC +05:30 Indian standard time)
At that time my database consumption reaches at its highest limit and I am getting performance issues with the system.
Can you guide me to configure same at midnight or between 1 AM to 5 AM (UTC +05:30), I mean how I can set that procedure time specific to prevent database load during pick hours ?
Any solution will be highly appreciable.