[ZBXNEXT-4110] Facebook MyRocks at MariaDB Created: 2017 Sep 19 Updated: 2019 Sep 11 |
|
| Status: | Postponed |
| Project: | ZABBIX FEATURE REQUESTS |
| Component/s: | API (A), Frontend (F), Server (S) |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Change Request | Priority: | Trivial |
| Reporter: | Oleg Egorov (Inactive) | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 5 |
| Labels: | MyRocks | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Epic Link: | DEV-677 |
| Description |
|
Facebook MyRocks is NoSQL database supported by MariaDB I think now it is best solution for history_text, history_log.... Easy to use and will be improved performance of Zabbix. MyRocks + Zabbix: Performance: |
| Comments |
| Comment by Vadims Kurmis [ 2019 Sep 11 ] |
|
Please ensure RocksDB support with updated documentation for making DB Schema. Because it Exactly matches Zabbix type of workload - for write-intensive applications. Strange, that this is not being prioritized yet as Zabbix development was always targeted for increased performance to compete with other products and provide a better and more robust solution. This is Critical, because Database always was a bottleneck for Zabbix.
|