how to fix wpf take up too much cpu on vmware

For some unknown reason, wpf may take up way to much cpu % on vmware, a workaround is to turn off hardware acceleration, add this dword value in the registry editor:
path: HKEY_CURRENT_USER\SOFTWARE\Microsoft\Avalon.Graphics\DisableHWAcceleration
value: 1
create the folder if not already exist.


Setup qemu and bridged network on ubuntu

Install qemu
apt-get install qemu-kvm virt-manager virt-viewer libvirt-bin bridge-utils
If it doesn’t work, use this:
apt-get install qemu-kvm qemu virt-manager virt-viewer libvirt-bin bridge-utils

Unfortunately, you don’t get the bridged network by default, so this is what has to be done:
stop network-manager
echo "manual" | tee /etc/init/network-manager.override

And you need to change your interface file like this:
auto br0
iface br0 inet static
bridge_ports eth0
bridge_stp on
bridge_maxwait 0
bridge_fd 0

Also add the ‘/etc/sysctl.conf’ settings to the end of the file:
net.bridge.bridge-nf-call-ip6tables = 0
net.bridge.bridge-nf-call-iptables = 0
net.bridge.bridge-nf-call-arptables = 0

Apply the changes:
sysctl -p /etc/sysctl.conf

To my surprise even this is needed:
Add to /etc/rc.local:
/sbin/sysctl -p /etc/sysctl.conf
iptables -A FORWARD -p tcp --tcp-flags SYN,RST SYN -j TCPMSS --clamp-mss-to-pmtu
exit 0

Root or run something like this:
ifdown eth0 && ifup br0

And last but not least, with br0, beloved eth0 seems gone forever, I don’t like this, but what other choice I have.

ubuntu boot into textmode

pico /etc/default/grub
And Do below changes:

Comment the line GRUB_CMDLINE_LINUX_DEFAULT=”quiet splash”, by adding # at the beginning, which will disable the Ubuntu purple screen.
Change GRUB_CMDLINE_LINUX=”” to GRUB_CMDLINE_LINUX=”text”, this makes Ubuntu boot directly into Text Mode.
Uncomment this line #GRUB_TERMINAL=console, by removing the # at the beginning, this makes Grub Menu into real black & white Text Mode (without background image)

And run this after:


A few mysql handy commands and useful tips to optimize speed

Show table schema and execution plan:
show create table
explain select

Index manipulation:
show index on drop index on create index on

show the running process:
show processlist

Also from stackoverflow:

Do you have an index on key_1?

Without it, each query by itself will already be slow just looking for 123.
Do you have an index on (key_1, key_2)?

Because select distinct key_2 where key_1 = 123 is really fast if it can get all the necessary data from the index alone. No need to access the table.
Are the rows/indexes fixed-size?

Traversing a fixed-size table/row can be faster because one always knows where the x-th record is by just calculating the offset. Variable row sized tables are slower.
Have you tried adding an autoincrement surrogate primary key?

Indexes work way better when all they have to store is the column, and a small primary key. Composite primary keys are slower.
Did you consider a read-only table?

You can pack myisam table for fast access, but they become read-only. It’s a hack that has its uses though.
One step further, have you considered a datawarehouse?

If the tables don’t change often, it might be best to duplicate the information for fast access.

Can you post a show create table statement? Seeing the columns and indexes would help. Can you post an explain select statement? Seeing which indexes are used would help.