David Hobach wrote:
You can see your pool driver by executing `qvm-pool`.
And the latest version of my scripts will always be available at [1].
Btw somehow one gets used to the worse performance after a while...
[1] https://github.com/3hhh/qubes-performance
Thank you very much.
And i
You can see your pool driver by executing `qvm-pool`.
And the latest version of my scripts will always be available at [1].
Btw somehow one gets used to the worse performance after a while...
[1] https://github.com/3hhh/qubes-performance
Mine currently looks like this:
Qubes release 4.1
David Hobach wrote:
There can be multiple reasons for a slower 4.1 experience. Known ones are:
1. CPU runs at ~800 MHz or so [1]
2. You're a file pool user. File pools were serialized in 4.1, likely
dropping their performance by ~30-50%. [2]
3. Possibly further issues in 4.1 [2].
[1]
There can be multiple reasons for a slower 4.1 experience. Known ones are:
1. CPU runs at ~800 MHz or so [1]
2. You're a file pool user. File pools were serialized in 4.1, likely dropping
their performance by ~30-50%. [2]
3. Possibly further issues in 4.1 [2].
[1]
Qubes wrote:
Qubes wrote:
Has the 4.1 as well as 4.1.1, because I did test on both, release
added additional overhead to the creation of a dvm?
I have identical dvm's for Firefox on 4.0 and 4.1 and on 4.1 it takes
almost, in the region of 0.5 - 0.75 seconds almost, **double** the
time for a
Qubes wrote:
Has the 4.1 as well as 4.1.1, because I did test on both, release added
additional overhead to the creation of a dvm?
I have identical dvm's for Firefox on 4.0 and 4.1 and on 4.1 it takes
almost, in the region of 0.5 - 0.75 seconds almost, **double** the time
for a new dvm to be
Has the 4.1 as well as 4.1.1, because I did test on both, release added
additional overhead to the creation of a dvm?
I have identical dvm's for Firefox on 4.0 and 4.1 and on 4.1 it takes
almost, in the region of 0.5 - 0.75 seconds almost, **double** the time
for a new dvm to be ready for
