This document discusses how an IT company called QUADRATA handled managing multiple remote Zabbix proxies in geographically distributed locations. They initially had issues with huge queues and busy sender processes due to network latency. They addressed this by installing NTP on all machines to synchronize time, optimizing the MySQL databases on proxies to use Percona Server and the innodb_file_per_table setting, and adjusting the DataSenderFrequency and ProxyOfflineBuffer settings to optimize sender processes. They also replicated the Zabbix frontend to account for multiple timezones and eventually migrated to Zabbix 3.0 for performance improvements in server-proxy communication.