database or storage engines. There are two main engines that you'll be interested in: InnoDB and MyISAM. Storage engines are transparent to the end user. MySQL will handle things differently under the them to one. • MyISAM is the older of the two. It can be faster than InnoDB under certain circumstances and favours a read only workload. Some web applications have been tuned around MyISAM (though that's imply that they will slow under InnoDB). MyISAM also supports the FULLTEXT data type, which allows very fast searches of large quantities of text data. However MyISAM is only capable of locking an entire table

configurations: Name Platform CPU/Memory Database Monitored hosts Small Ubuntu Linux PII 350MHz 256MB MySQL MyISAM 20 Medium Ubuntu Linux 64 bit AMD Athlon 3200+ 2GB MySQL InnoDB 500 Large Ubuntu Linux 64 bit frontend. It may be practical to use less powerful hardware with Zabbix server running SQLite or MySQL MyISAM while nodes of higher levels may use combination of a better hardware with MySQL InnoDB, Oracle world configuration Server with Zabbix 1.0 installed (RedHat Linux 8.0, kernel 2.4.18-14, MySQL/MyISAM 3.23.54a-4, Pentium IV 1.5Ghz, 256Mb, IDE) is able to collect more than 200 parameters per second

database or storage engines. There are two main storage engines that you’ll be interested in: InnoDB and MyISAM. Storage engines are transparent to the end user. MySQL will handle things differently under the them to one. • MyISAM is the older of the two. It can be faster than InnoDB under certain circumstances and favours a read-only workload. Some web applications have been tuned around MyISAM (though that’s that they will be slower under InnoDB). MyISAM also supports the FULLTEXT data type, which allows very fast searches of large quantities of text data. However MyISAM is only capable of locking an entire table

• for MySQL, use InnoDB table structure • ZABBIX works at least 1.5 times faster (comparing to MyISAM) if InnoDB is used. This is because of increased parallelism. However, InnoDB requires more CPU

• for MySQL, use InnoDB table structure • ZABBIX works at least 1.5 times faster (comparing to MyISAM) if InnoDB is used. This is because of increased parallelism. However, InnoDB requires more CPU

• for MySQL, use InnoDB table structure • ZABBIX works at least 1.5 times faster (comparing to MyISAM) if InnoDB is used. This is because of increased parallelism. However, InnoDB requires more CPU

当前由开源社区进行维护，是 MySQL 的分支产品，而且与 MySQL 具有高度的 兼容性，与 MySQL API 和命令均保持一致。并且 MariaDB 还自带了一个新的存储引擎 Aria， 用于替代 MyISAM。因此，MariaDB 与 MySQL 一样好用。 与此同时，由于各大公司之间存在着竞争关系或利益关系，外加 MySQL 在被收购之后逐渐 由开源向闭源软件转变，很多公司抛弃了 MySQL。当前，谷歌、维基百科等决定将

• for MySQL, use InnoDB table structure • ZABBIX works at least 1.5 times faster (comparing to MyISAM) if InnoDB is used. This is because of increased parallelism. However, InnoDB requires more CPU

• for MySQL, use InnoDB table structure • ZABBIX works at least 1.5 times faster (comparing to MyISAM) if InnoDB is used. This is because of increased parallelism. However, InnoDB requires more CPU

• for MySQL, use InnoDB table structure • ZABBIX works at least 1.5 times faster (comparing to MyISAM) if InnoDB is used. This is because of increased parallelism. However, InnoDB requires more CPU