Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow system RAM target to be set using absolute values #784

Closed
KodrAus opened this Issue Jan 14, 2019 · 5 comments

Comments

Projects
None yet
3 participants
@KodrAus
Copy link
Member

KodrAus commented Jan 14, 2019

It would be useful for some environments, like Kubernetes, to be able to limit Seq's target memory utilisation (as set by cache.systemRamTarget) based on an absolute value, like 500m, instead of a percentage of the reported system total.

@nblumhardt nblumhardt added this to the 5.1-pre milestone Jan 14, 2019

@SeriousM

This comment has been minimized.

Copy link

SeriousM commented Jan 16, 2019

I would suggest that the value can be configured in Seq.json as well as an overruling environment variable to ease the configuration in docker/k8s pods.

@KodrAus KodrAus closed this Jan 22, 2019

@SeriousM

This comment has been minimized.

Copy link

SeriousM commented Mar 4, 2019

Hi @KodrAus, is this change in any of the latest versions? (5.0.2787, 5.0.2817)
How can I use it?

@KodrAus

This comment has been minimized.

Copy link
Member Author

KodrAus commented Mar 7, 2019

Hi @SeriousM, you can use an absolute value in one of the 5.1 preview builds. Setting the system RAM target to a value greater than 1 will be treated as a target in bytes instead of a fraction of total available memory.

@SeriousM

This comment has been minimized.

Copy link

SeriousM commented Mar 7, 2019

That's good to know, but is 5.1pre RTM? We need it on the production server and want to avoid any downtime.

@nblumhardt

This comment has been minimized.

Copy link
Member

nblumhardt commented Mar 8, 2019

Hi @SeriousM - no, 5.1 is currently pre-release, but we're aiming for a final build within the month, if all goes to plan. We won't be able to get this into a 5.0 build any sooner, so using the pre-release build of 5.1 or waiting until it's released is the best we can do right now, sorry. HTH!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.