How guarantee a responsive Desktop using cgroup memory limit
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
I would like to setup a system with limited memory (raspberry pi) in such a way that application can't cause the desktop (x11, LXDE, openbox, mouse driver, video card driver) to be unresponsive.
When I open too many browser tab the browser use too much memory and cause Linux to swap pages to disk. Some of the pages can belong to the desktop ... which result in the keyboard or mouse input to lag significantly making it impossible to open task-manager and decide which application to kill.
If after a fresh boot, the Desktop need 200MB of memory and the machine have a total of 1GB of memory.
Is it possible to put all application started after boot in CGROUP limited to 800MB of memory such that when any memory hungry process in this CGROUP exceed 800MB it would not evict any memory pages needed for the desktop to stay responsive?
I dont want to disable SWAP completely, I think it's better for memory Hungry application to swap and become slow instead of getting killed by oom-killer. As long as the desktop itself does not become slow.
linux virtual-memory memory-management container
asked Feb 11 at 19:15
skydeskyde
1063
add a comment |
I would like to setup a system with limited memory (raspberry pi) in such a way that application can't cause the desktop (x11, LXDE, openbox, mouse driver, video card driver) to be unresponsive.
When I open too many browser tab the browser use too much memory and cause Linux to swap pages to disk. Some of the pages can belong to the desktop ... which result in the keyboard or mouse input to lag significantly making it impossible to open task-manager and decide which application to kill.
If after a fresh boot, the Desktop need 200MB of memory and the machine have a total of 1GB of memory.
Is it possible to put all application started after boot in CGROUP limited to 800MB of memory such that when any memory hungry process in this CGROUP exceed 800MB it would not evict any memory pages needed for the desktop to stay responsive?
I dont want to disable SWAP completely, I think it's better for memory Hungry application to swap and become slow instead of getting killed by oom-killer. As long as the desktop itself does not become slow.
linux virtual-memory memory-management container
asked Feb 11 at 19:15
skydeskyde
1063
add a comment |
I would like to setup a system with limited memory (raspberry pi) in such a way that application can't cause the desktop (x11, LXDE, openbox, mouse driver, video card driver) to be unresponsive.
When I open too many browser tab the browser use too much memory and cause Linux to swap pages to disk. Some of the pages can belong to the desktop ... which result in the keyboard or mouse input to lag significantly making it impossible to open task-manager and decide which application to kill.
If after a fresh boot, the Desktop need 200MB of memory and the machine have a total of 1GB of memory.
Is it possible to put all application started after boot in CGROUP limited to 800MB of memory such that when any memory hungry process in this CGROUP exceed 800MB it would not evict any memory pages needed for the desktop to stay responsive?
I dont want to disable SWAP completely, I think it's better for memory Hungry application to swap and become slow instead of getting killed by oom-killer. As long as the desktop itself does not become slow.
linux virtual-memory memory-management container
asked Feb 11 at 19:15
skydeskyde
1063
I would like to setup a system with limited memory (raspberry pi) in such a way that application can't cause the desktop (x11, LXDE, openbox, mouse driver, video card driver) to be unresponsive.
When I open too many browser tab the browser use too much memory and cause Linux to swap pages to disk. Some of the pages can belong to the desktop ... which result in the keyboard or mouse input to lag significantly making it impossible to open task-manager and decide which application to kill.
If after a fresh boot, the Desktop need 200MB of memory and the machine have a total of 1GB of memory.
Is it possible to put all application started after boot in CGROUP limited to 800MB of memory such that when any memory hungry process in this CGROUP exceed 800MB it would not evict any memory pages needed for the desktop to stay responsive?
I dont want to disable SWAP completely, I think it's better for memory Hungry application to swap and become slow instead of getting killed by oom-killer. As long as the desktop itself does not become slow.
linux virtual-memory memory-management container
linux virtual-memory memory-management container
asked Feb 11 at 19:15
skydeskyde
1063
asked Feb 11 at 19:15
skydeskyde
1063
asked Feb 11 at 19:15
skydeskyde
1063
asked Feb 11 at 19:15
skydeskyde
1063
asked Feb 11 at 19:15
skydeskyde
1063
1063
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1404557%2fhow-guarantee-a-responsive-desktop-using-cgroup-memory-limit%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1404557%2fhow-guarantee-a-responsive-desktop-using-cgroup-memory-limit%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
