Jump to: navigation, search

Tuning

Tuning[edit]

Introduction[edit]

Everything absolutely optional. Mostly largely untested!

At the top of the Tuning chapter are the easier tuning steps. The farther you go down, the more skill will be required.

Increase Virtual Machine RAM[edit]

If less important identifiers are not important to you, and this is most likely very unimportant, you could use VirtualBox settings and increase the RAM for your Virtual Machine(s). Whonix-Workstation will profit most, if you run into low RAM. Also Whonix-Gateway could profit if you are creating big numbers of circuits and keep Tor busy. You can check how much RAM is free using free -m in Terminal.

More CPU cores[edit]

On systems with multi-core processors, if less important identifiers are not important to you, and this is most likely unimportant, you could increase the number of cores available to the Virtual Machine(s) in VirtualBox settings.

Removing packages[edit]

For example you could experiment with uninstalling Nepomuk and virtuoso.

Replacing Desktop Environment[edit]

You could even uninstall KDE and use your own desktop environment or only cli. See Other Desktop Environments.

Synthetic CPU[edit]

If less important identifiers are not important to you, you could try if deactivating the Synthetic CPU increases performance for you.

VBoxManage modifyvm "Whonix-Workstation" --synthcpu off

VBoxManage modifyvm "Whonix-Gateway" --synthcpu off

Nested paging and VPIDs[edit]

You could increase performance by using Nested paging and/or VPIDs. It is unknown, if that may decrease security or stability. See VirtualBox manual: Nested paging and VPIDs for more information.

vboxmanage modifyvm Whonix-Workstation --largepages on

vboxmanage modifyvm Whonix-Gateway --largepages on

vboxmanage modifyvm Whonix-Workstation --vtxvpid on

vboxmanage modifyvm Whonix-Gateway --vtxvpid on

Hardware-accelerated graphics[edit]

Requires Guest Additions, therefore not recommended, see above. Can increase performance.

See VirtualBox manual: Hardware-accelerated graphics.

Memory ballooning, Page Fusion, Memory overcommitment[edit]

Requires Guest Additions, therefore not recommended, see above. Can increase performance.

See VirtualBox manual: Memory overcommitment.

64 bit architecture[edit]

Several methods. The last method is probably the most useful one.

Maybe it would enhance security and/or performance by using an amd64 kernel. How much sense that makes when the rest of the system is still 32 bit?

sudo apt-get install linux-image-amd64

You could try to Debian Multiarch HOWTO.

Or better create amd64 builds yourself from source.

Optimized builds[edit]

Since the concept behind Whonix isn't tied to anything, you could create your own implementation. Perhaps using Gentoo with optimized build flags for your system. See Whonix Framework, OneVM and Hardened Gentoo TG.

PCI passthrough[edit]

Might greatly improve graphics performance. Might have security implications.

Essentially this feature allows to directly use physical PCI devices on the host by the guest even if host doesn't have drivers for this particular device. See VirtualBox Manual: PCI passthrough.


Random News:

Please consider a recurring donation!


Impressum | Datenschutz | Haftungsausschluss

https | (forcing) onion
Share: Twitter | Facebook | Google+
This is a wiki. Want to improve this page? Help welcome, volunteer contributions are happily considered! See Conditions for Contributions to Whonix, then Edit! IP addresses are scrubbed, but editing over Tor is recommended. Edits are held for moderation. Whonix (g+) is a licensee of the Open Invention Network. Unless otherwise noted above, content of this page is copyrighted and licensed under the same Free (as in speech) license as Whonix itself.