On 08/13/2018 03:26 AM, Kelly Dean wrote:
Unman writes:
I don't recognise this on a somewhat under powered laptop with HDD -
definitely not "minutes at a time". Is there something significant about
the disks that you cite, or are those just examples?
Nothing significant about #21 in particular. The thrashing procs are whichever
ones handle the virtual disks for a qube that's thrashing.
System is a core i3 with 16GB RAM, and HD with about 100MB/s throughput.
Worst problems seem to be from swapping, and random times when I start a qube.
The swapping is unpredictable, but here's a typical best-case result for
starting an ordinary app qube with fedora-28 template:
T+0: start qube. Brief burst of CPU & disk activity for a second, then mostly
idle for 20 seconds.
T+20: heavy sustained disk thrashing starts.
T+40: pop-up notification that the domain has started. Thrashing continues.
T+60: thrashing abruptly stops.
That's only 1 minute, but when I'm unlucky, it can be several minutes.
How does that compare with your experience?
I don't have anything custom configured to run in the qube at startup, so all
the activity is from the template's defaults. Nothing special about fedora-28
either; I get similar results from debian-9 and whonix-ws.
Can Qubes access all of that RAM? Look at the total_memory figure from
'xl info'.
--
Chris Laprise, tas...@posteo.net
https://github.com/tasket
https://twitter.com/ttaskett
PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/7a4a0c2c-7294-5a37-10d0-0615185a3073%40posteo.net.
For more options, visit https://groups.google.com/d/optout.
