Currently, Zabbix server caches information about items, hosts, templates, interfaces, and macros (in trunk; in 1.8 it caches less). That cache is updated every CacheUpdateFrequency seconds. It would be nice if Zabbix server would cache information about triggers, too, so that it would not have to fetch trigger information from the database for every historical value it processes.