Previously, in large environments the delete job took longer than it should have (around 5 hours). This caused a load on the sampling process, data was not deleted, and a backlog was created for large sampling tables such as vm_interface_samples_history and vm_disk_samples_history. This release adds a mechanism that will allow the samples deletion process to become more aggressive according to the following parameters: the number of times the deletion loop runs; the Initial and Increment values; and the number of iterations between increments. In addition, the DWH_LIMIT_ROWS parameter enables updating the hourly and daily deletion process with the amount of rows to be deleted in each iteration. The deletion process is now more dynamic, and can be customized according to the environment, so the delete process will not take longer than 5 hours.