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

qmemman should do everything it can to avoid swapping in VMs #308

Closed
marmarek opened this Issue Mar 8, 2015 · 4 comments

Comments

Projects
None yet
2 participants
@marmarek
Member

marmarek commented Mar 8, 2015

Reported by joanna on 23 Jul 2011 18:33 UTC
When an AppVM starts using its swap (as seen via free) it slows down dramatically...

Migrated-From: https://wiki.qubes-os.org/ticket/308

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Mar 8, 2015

Member

Comment by rafal on 25 Jul 2011 07:51 UTC
Any more precise suggestions ?
If VM starts swapping, it means qmmeman is not able to give it more memory, because other domains are already not above their preferred memory size. In such condition, if we take memory from some other VM, this other VM can start swapping, too.

Member

marmarek commented Mar 8, 2015

Comment by rafal on 25 Jul 2011 07:51 UTC
Any more precise suggestions ?
If VM starts swapping, it means qmmeman is not able to give it more memory, because other domains are already not above their preferred memory size. In such condition, if we take memory from some other VM, this other VM can start swapping, too.

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Mar 8, 2015

Member

Comment by joanna on 25 Jul 2011 08:21 UTC
Such as: determine if there are "unused" AppVMs running (unused =def= those that have not got any GUI window displayed for the last N minutes), and shut them down.

It really gets easy to end up having some ten or more AppVMs running, while most of them not used at all for a few days.

The price we pay is that perhaps the user would need to wait some... 12 secs when starting an app from one of those closed AppVMs -- but we minimize chances of one of the used AppVMs to become effectively unusable.

Moving this to Beta 3. Perhaps this would nicely fit into ticket #207.

Member

marmarek commented Mar 8, 2015

Comment by joanna on 25 Jul 2011 08:21 UTC
Such as: determine if there are "unused" AppVMs running (unused =def= those that have not got any GUI window displayed for the last N minutes), and shut them down.

It really gets easy to end up having some ten or more AppVMs running, while most of them not used at all for a few days.

The price we pay is that perhaps the user would need to wait some... 12 secs when starting an app from one of those closed AppVMs -- but we minimize chances of one of the used AppVMs to become effectively unusable.

Moving this to Beta 3. Perhaps this would nicely fit into ticket #207.

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Mar 8, 2015

Member

Modified by joanna on 25 Jul 2011 08:21 UTC

Member

marmarek commented Mar 8, 2015

Modified by joanna on 25 Jul 2011 08:21 UTC

@marmarek marmarek added enhancement and removed bug labels Mar 8, 2015

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Mar 8, 2015

Member

Modified by joanna on 25 Sep 2011 10:53 UTC

Member

marmarek commented Mar 8, 2015

Modified by joanna on 25 Sep 2011 10:53 UTC

@marmarek marmarek added the wontfix label Mar 8, 2015

@marmarek marmarek closed this Mar 8, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment