Nagios Support Forum

I found a similar thread https://support.nagios.com/forum/viewto ... 38&t=40512 that explains the RAM usage is meant to be high, but since it's been almost 4 years and I'm a new user of Log Server I just wanted to ask in this new thread.

Is there a proper way to lower the RAM usage (ideally not a hack)?

In our case, response time (that Nagios Log Server does the analysis and notifies) doesn't have to be super fast. We can even start from receiving reports hourly or so. So hopefully this relaxed usecase can help lowering system's operation bandwidth, but I'm not sure.

I'm still figuring out usecases for our production system, but if the RAM usage is meant to occupy this lot, it'd raise the the bar fairly high for deploying Log Server as part of our solution (although we like the functionalities).

```
$ sudo /usr/local/nagios/bin/nagios --version

Nagios Core 4.4.5
Copyright (c) 2009-present Nagios Core Development Team and Community Contributors
Copyright (c) 1999-2009 Ethan Galstad
Last Modified: 2019-08-20
License: GPL
```

Hello, welcome to the forum! And thank you for doing a search before posting! Often times you can find the solution to problems that way.

Regarding the RAM usage, that is fairly normal. Java, in the back end, is automatically set to consume about 50% of your system memory, so that's 8 of the 12GB used right there.

Like any other database software, the database back end in Log Server is going to put as much data in memory as humanly possible. If you have a lot of system memory, it will use a lot of memory, and your queries will be generally fast. If you don't have a lot of system memory, Log Server will still use as much as it can, and do the best it can for query performance.

You have a number of options for tuning performance with Log Server. Aside from things like disk topology, or adding instances to a Log Server cluster, you can specify the number of open indexes. This limits the amount of in-memory data, essentially allowing Log Server to do more with less. How many open indexes do you currently have? Also what is the Primary Size and Total Size shown in your index statistics? You can get all of this information from Admin -> Index Status.