Commit graph

16 commits

Author SHA1 Message Date
Noi
2977ae61f1 Whitespace and style fixes 2024-04-28 01:51:58 -07:00
Noi
41def830c4 Only remove data from guilds in own shard 2023-12-08 20:44:42 -08:00
Noi
b87602f8f6 Greatly reduce frequency of stale entry removal 2023-09-04 17:40:56 -07:00
Noi
b0b39bbd0b Allow configuration of certain time-based values 2023-05-27 18:07:45 -07:00
Noi
a3ac5d6ede Change data types from long to ulong 2022-11-22 23:19:37 -08:00
Noi
2c920e9794 Upgrade EFCore, switch to bulk operations 2022-11-21 21:20:48 -08:00
Noi
31d5513c9e Reduce concurrent database operations in background services 2022-08-09 17:05:19 -07:00
Noi
c280904cb8 Update services to use EF queries 2022-03-21 12:12:18 -07:00
Noi
3741222c68 Improve performance by placing updates in transaction 2021-12-05 18:29:27 -08:00
Noi
f8350fed53 Increase threshold, no longer stagger DataRetention
This staggering was most likely the cause of a major amount of data lost recently, in which certain guilds never had their values updated.
The staggering was meant to attempt to reduce load on a server with limited capabilities, and testing shows that it runs on more capable hardware without this issue when run this way.
2021-11-22 11:49:55 -08:00
Noi
6f34fbe657 Modified all background services
-Removed a number of diagnostic messages
-Removed ConnectionStatus, connection scores, etc.
-Modified work intervals for certain background tasks
-Updated code style
2021-10-14 18:55:04 -07:00
Noi
dcb9bfdd9a Apply suggestions from code analysis 2021-10-13 20:38:52 -07:00
Noi
57a870efda Additional diagnostic information 2021-10-13 19:28:00 -07:00
Noi
1e8b47784d Modify DataRetention behavior; simplify SQL config 2021-02-01 22:03:50 -08:00
Noi
a631f55a37 Change exception type thrown by semaphore 2020-10-25 13:44:35 -07:00
Noi
9ef164bac1 Update DataRetention service
Renamed from StaleDataCleaner.
Modified to run only once concurrently, to not put extra load on the
database connection pool.
2020-10-09 23:57:30 -07:00