Fri Apr 15, 2016 6:25 am
keep an eye on dude database size, i always try to keep it at maximum 500mbytes to maintain a good performance, i prefer to split the work between multiple virtual machines to establish multiple instances of the dude, one instance on every virtual machine, that way i distribute the work, taking in count the dude is single threaded with multiple instances you can take advantage of a multi-core server using the dude
i think beyond 500mb it gets very i/o intensive for the storage of the machine running dude server for some tasks
make periodic backups to be prepared in case of database corruption
i think the performance of the dude do not depend directly of how many devices you have on it, i think it depends of how many services and probes are you monitoring and how many time of data are you keeping, for example keeping 100 services keeping 14 days of raw data is a heavy task and consumes 500mb of database.
if you maintain less raw data you reduce a lot the load and size of the database, but your graphics are less accurate when you try to see old data beyond the raw interval you are keeping