Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletter Hub
Free Learning
Arrow right icon
timer SALE ENDS IN
0 Days
:
00 Hours
:
00 Minutes
:
00 Seconds
Arrow up icon
GO TO TOP
Zabbix Performance Tuning

You're reading from   Zabbix Performance Tuning Tune and optimize Zabbix to maximize performance

Arrow left icon
Product type Paperback
Published in Jun 2015
Publisher
ISBN-13 9781783987641
Length 152 pages
Edition 1st Edition
Tools
Arrow right icon
Author (1):
Arrow left icon
Luciano Alves Luciano Alves
Author Profile Icon Luciano Alves
Luciano Alves
Arrow right icon
View More author details
Toc

Table of Contents (20) Chapters Close

Zabbix Performance Tuning
Credits
Foreword
About the Author
Acknowledgements
About the Reviewers
www.PacktPub.com
Preface
1. Evolution of Zabbix FREE CHAPTER 2. Zabbix and I – Almost Heroes 3. Tuning the Zabbix Server 4. Tuning the MySQL Database 5. Tuning the Frontend 6. Adjusting the Storage 7. Tuning the Operating System 8. Doing the Extra Work 9. Using the Zabbix Proxy 10. Monitoring the Health of Zabbix 11. The Next Challenge Index

DBSyncers – the unknown bottleneck


With the introduction of caches and buffers (in Zabbix version 1.8), it was necessary to create an internal process that could control the data entering and leaving these caches and buffers. In practice, we have two processes responsible for data management:

  • Configuration syncer:

    • This process manages the cache of configuration data.

    • It's a unique process (it is neither necessary nor possible to increase the amount of syncer).

    • The time of the sync data is controlled by the CacheUpdateFrequency parameter (zabbix_server.conf). By default, this time is set to 60 seconds.

  • History syncer:

    • This writes the gathered data to the database

    • As a standard, we have four processes that can (and usually should) be changed to a higher or lower value, depending on the necessity and limitations of the environment

    • The syncing time for the data gathered is 5 seconds for each DBSyncer, and it can't be changed by the user

    • The number of DBSyncers is controlled by the StartDBSyncer parameter...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at £13.99/month. Cancel anytime
Visually different images