Actually the Zabbix Housekeeper is working very well with normal operations, cleaning item values but i can't say the same when we delete some prototype items or simple items.

During an official Zabbix issue we are now know the right meaning of the MaxHousekeeperDelete parameter, this variable only affect the amount of value of a deleted item per Housekeeper run.

For example if i have a template for Cisco Switches with some Item prototype related to the port metrics, you will probably face this numbers:
N.1 Item prototype expanded with 100 switch ports x 10 monitored Switches => 1000 Discovered Items x Update interval
In this case Zabbix Housekeeper wil try to remove n. MaxHousekeeperDelete (ex.500) x Total Discovery Items (1000) => 500k history value in a single run.

So the MaxHousekeeperDelete don't limit the query for a single Housekeeper run and in some case this logic can dramatically increase the workload of Zabbix Server.

Please provide a better documentation of the MaxHousekeeperDelete or much more Predictable logic of Housekeeper process operation.