Make it possible to enter RAM value instead of using slider

[jdaviescoates]

I find the sliders for allocating RAM to apps/ servers a bit too annoying to use. It's often really quite hard to get the value I want.

I would much prefer to simply be able to enter a number into a field.

Please could we have this option in addition to the existing sliders?

Thanks!

[nebulon]

Given how memory management on Linux works, this limit is merely a rough setting on the limit, it makes no sense on Linux to rely on explicit numbers there but it is more about the ballpark to get right. The value should not convey false correctness and the stop gaps on the slider are just for neatness on the value.

[jdaviescoates]

@nebulon OK, I don't fully follow you, but right now getting the right ballpark figures is too hard using the sliders.

If you can't/ wont add a field we can just type into perhaps add little up/down arrows or something to enable nudging the value up/down in tiny increments?

[jdaviescoates]

Just chiming in again to say again that the existing RAM sliders are a bad UX

[IniBudi]

Yes, I agree. Sometimes it's difficult to set RAM usage because of the sliders. I prefer if there's an option to just type the number.

[nebulon]

So for next release we will move to the browser native slider element, which gives better accessibility and slightly better behavior:

[vividly8450]

Great to hear. I was just on my way to the forum to make this exact same request.

I understand that this is not an exact setting; setting the memory limit to 4 GB does not guarantee that the app will never use more than 4096 megabytes of RAM. However, this also means that there's also no benefit to allowing values like "3.86 GB". Having all those extra steps in between each value is only a mild annoyance at worst, but I'd still prefer the ability to type in a value or have it stop every .25 GB or even .5 GB.

I also guarantee that whatever interval you set, you'll also get feature requests asking for more granularity.

[nebulon]

Given that those values are not exact anyways giving the user a false feeling is also wrong.

I guess https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input/range has the wording indicating the widget is the correct one to use here: Because this kind of widget is imprecise, it should only be used if the control's exact value isn't important.