Best configuration for 512MB RAM?

[Tom Maiaroto]

I'm running InfluxDB on a very small server. I have a few other processes
running, but nothing crazy.
What would the best settings be for small servers?

I noticed sometimes InfluxDB is not running and I can't find any reasoning
in the logs. So I figured it was running out of memory.
I haven't profiled, but will set something up.

In general though, are there any good approximations I can use in the
config?
ie. multiple this number of open files by available memory and that will
give you the max open files.... etc.

Aside from max-open-files ... are there any other settings to tweak?

What about LRU cache size?

Any tips would be great, thanks!
Also, is there a minimum amount of RAM suggested for running InfluxDB?

[p***@gmail.com]

I'm running InfluxDB (default config plus the graphite input plugin) and a collectd daemon and some other stuff on one 512MB cloud server and so far so good. The influxdb daemon also receives system metrics data from 2 other cloud servers running collectd.

The influxdb daemon uses +-60MB memory.

[Tom Maiaroto]

Hmmm, well I'm using Go... Maybe I should use some Http Client other than
the default. Maybe something is being left open even.

I'm still curious about what the settings would do and if any would help.
I'm assuming 512MB was not the target amount of RAM for the database and
those settings are based on having more, no?

Post by Tom Maiaroto
I'm running InfluxDB on a very small server. I have a few other processes
running, but nothing crazy.
What would the best settings be for small servers?
I noticed sometimes InfluxDB is not running and I can't find any reasoning
in the logs. So I figured it was running out of memory.
I haven't profiled, but will set something up.
In general though, are there any good approximations I can use in the
config?
ie. multiple this number of open files by available memory and that will
give you the max open files.... etc.
Aside from max-open-files ... are there any other settings to tweak?
What about LRU cache size?
Any tips would be great, thanks!
Also, is there a minimum amount of RAM suggested for running InfluxDB?

[Heath Raftery]

Bump. A reasonable query I think, because running with 512MB opens up a
whole different universe of hosts for users with simple requirements.

My experience is with a default install of influxdb 1.1.1, grafana 4.0.2
and kapacitor 1.1.1. Points arrive via HTTP at about 2500/day. There's two
databases with series cardinality of 21 and 1 (the latter is for grafana
annotations), plus the _internal database with 188. Other than manual
viewing of data with grafana, the only other non-default queries are made
by a kapacitor script that processes the stream from one measurement and
writes to another.

I'm running with 512MB, and every week or so Influx quietly dies, with an
OOM message left in syslog. Runs perfectly fine on restart, with about
150MB free (as reported by free -m).

Given how outrageously far I am from sweating influxdb's capabilities (the
hardware sizing guidelines start at series cardinality of 100,000), it
seems there ought to be a configuration that will happily run on 512MB.

Rolf, your results are impressive. Have you noticed much change over time?

Heath

Post by Tom Maiaroto
I'm running InfluxDB on a very small server. I have a few other processes
running, but nothing crazy.
What would the best settings be for small servers?
I noticed sometimes InfluxDB is not running and I can't find any reasoning
in the logs. So I figured it was running out of memory.
I haven't profiled, but will set something up.
In general though, are there any good approximations I can use in the
config?
ie. multiple this number of open files by available memory and that will
give you the max open files.... etc.
Aside from max-open-files ... are there any other settings to tweak?
What about LRU cache size?
Any tips would be great, thanks!
Also, is there a minimum amount of RAM suggested for running InfluxDB?

[r***@gmail.com]

Post by Heath Raftery
Rolf, your results are impressive. Have you noticed much change over time?

The system is stable over time. The metrics server is restarted once a week for an offline backup.

We are using the db since 2014 and we recently upgraded Grafana V2.0 to V4.x and InfluxDB V0.8 to V1.1.1 and it still works fine on that 512MB box.

It currently collects 200 server telemetry metrics from each of the 5 cloud servers at 10 seconds intervals, and 25 functional metrics for airport take-off and landing metrics at 30 seconds intervals.

--
Rolf