Graylog solution sizing on an ESXi server

It’s about a year since I started using Graylog as a stand-alone solution on a single ESXi server with 16 Xeon CPUs and 143G of RAM. Until now we could process about 5.000 messages per second but now we would like to add new sources (8.000 messages per second) and the application seems to degrade despite the tuning attempts. Which solution is preferable? It’s a good idea to split Graylog/MongoDB from Elasticserarch using two different virtual servers?

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.