This repository has been archived by the owner on May 26, 2021. It is now read-only.
limit swap partition size to 8 GiB #8
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The swap calculation is probably from the i386 days. Capping seems reasonable, but I’m not sure about 4GB as the recommended value was always 2 times RAM, which for i386 creates a max of 8GB.
So from a historical standpoint we do not only cap the swap size, but we reduce its old maximum by half.
Change to 8GB?
… On 14. Nov 2017, at 04:51, Frank Wall ***@***.***> wrote:
I had an interesting experience: I've installed OPNsense on a server with 32 GiB RAM and a 128 GiB SSD as boot device. This resulted in a whopping 64 GiB swap partition! Not useful at all. This should not be the result of the default/easy installation.
The initial swap partition should be sort of a last resort and thus be rather small. I suggest to limit it's size to 4 GiB. It's still possible to add additional swap files later, if the need arises, and I think this should be the preferred way.
You can view, comment on, or merge this pull request online at:
#8
Commit Summary
limit swap partition to 4 GiB
File Changes
M installer/conf/Product.lua (4)
Patch Links:
https://github.com/opnsense/bsdinstaller/pull/8.patch
https://github.com/opnsense/bsdinstaller/pull/8.diff
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
A good compromise. Although, if a server actually uses this amount of swap space, it's pretty much useless anyway ;) |
fraenki
changed the title
|
Changed it to 8 GiB in e8681c1. |
|
Merged, thanks. Someone else in the forum asked for the same issue. What do you think about asking for swap creation but still set the default to use a swap? This way we could also tell people a swap can’t be created because too small. |
It's always good to have a choice. So yes, asking this question during installation would certainly be an improvement. |
|
Ok, I’ll give this more thought. Thanks for the input. :) |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I had an interesting experience: I've installed OPNsense on a server with 32 GiB RAM and a 128 GiB SSD as boot device. This resulted in a whopping 64 GiB swap partition! Not useful at all. This should not be the result of the default/easy installation.
The initial swap partition should be sort of a last resort and thus be rather small. I suggest to limit it's size to 4 GiB. It's still possible to add additional swap files later, if the need arises, and I think this should be the preferred way.