Hello!
This is a very complicated question. There's no direct relationship proven. Usually, this will depend on the status of the job after execution. Normally, failed jobs will remain in the list consuming storage. As a safe practice, you should review failed jobs periodically and then, after solving any issue that might have caused them, remove them.
However, if we leave the number of records on certain tables to grow (ActivityPointer, etc), besides the extra storage, it means that everytime system requires something from this table, it will have more and more records to query. It's not the same to run a query over 200K records than doing it on 2 million. Specially, because the larger the number of records the larger the indexes required. And because there's a view of "failed system jobs", this will consume more storage and queries will be slightly slower.
However, there are certain jobs that instead of being moved to "failed" remain as "waiting". And these are the dangerous ones, because it means they might be reprocessed.
Regards,
******
I hope this answer has helped you solve your problem. If you are satisfied with it, please consider marking it as the excellent answer by clicking on the green check mark below. This will help other users who have similar questions find the best solution.
Thank you for your feedback!
Share
Report
19
All responses (
Answers (
