Hi Servicenow enthusiast,
Just a bit curious about what factors decide the number of records archived per hourly execution of a archival rule. The documentation says that the entire archival job is divided into 10 batches with each batch archiving 100 records - This is the expectation if the following properties are untouched.
1) glide.db.archive.max_iterations - 10
2) glide.db.archive.batch_size - 100
The results were surprising when I run a simple archival rule on change request table with a condition "closed in this year". We had 5.9 k records to archive but it took only 6 batches to complete the archival - 5 batches archiving 1000 records each and the 6th one 900 in a SINGLE RUN!!.
In short, there was a multiplication factor or something that scaled the number of records archived per each batch execution. Here is how I was anticipating the system would work.
100 records X 10 batch = 1000 records in 1 hour
Total executions required = Total number of records/Number of records archived hourly=5900/1000 ~ 6
Hence, it takes 6 hours to complete the archival of all records.
Can somebody explain what is happening? Please correct me if the way I think is wrong.
