hmm gave it a shot on my machine on eth0 (since I go out via a smoothy). set it up for 64K, since I'm only on ISDN, damn you BT for not installing ADSL in my area.
Okay I chose 212.140.212.13 as my ip to ping since it was the next hop after my smoothie.
Normal (i.e no downloads going on)
bash-2.05a$ ping 212.140.212.13
PING 212.140.212.13 (212.140.212.13): 56 octets data
64 octets from 212.140.212.13: icmp_seq=0 ttl=254 time=70.8 ms
64 octets from 212.140.212.13: icmp_seq=1 ttl=254 time=67.3 ms
64 octets from 212.140.212.13: icmp_seq=2 ttl=254 time=63.1 ms
64 octets from 212.140.212.13: icmp_seq=3 ttl=254 time=65.1 ms
64 octets from 212.140.212.13: icmp_seq=4 ttl=254 time=61.3 ms
64 octets from 212.140.212.13: icmp_seq=5 ttl=254 time=93.2 ms
64 octets from 212.140.212.13: icmp_seq=6 ttl=254 time=82.6 ms
64 octets from 212.140.212.13: icmp_seq=7 ttl=254 time=67.0 ms
64 octets from 212.140.212.13: icmp_seq=8 ttl=254 time=69.0 ms
--- 212.140.212.13 ping statistics ---
9 packets transmitted, 9 packets received, 0% packet loss
round-trip min/avg/max = 61.3/71.0/93.2 ms
I downloaded a mp3 off of a m8 to give this thing a whirl, in the end it averaged 5.34K/sec.
Ping without Wonder shaper
bash-2.05a$ ping 212.140.212.13
PING 212.140.212.13 (212.140.212.13): 56 octets data
64 octets from 212.140.212.13: icmp_seq=0 ttl=254 time=1172.5 ms
64 octets from 212.140.212.13: icmp_seq=1 ttl=254 time=1268.9 ms
64 octets from 212.140.212.13: icmp_seq=2 ttl=254 time=1371.7 ms
64 octets from 212.140.212.13: icmp_seq=3 ttl=254 time=1468.1 ms
64 octets from 212.140.212.13: icmp_seq=4 ttl=254 time=1562.7 ms
64 octets from 212.140.212.13: icmp_seq=5 ttl=254 time=1661.8 ms
64 octets from 212.140.212.13: icmp_seq=6 ttl=254 time=1755.3 ms
64 octets from 212.140.212.13: icmp_seq=7 ttl=254 time=1844.7 ms
64 octets from 212.140.212.13: icmp_seq=9 ttl=254 time=2071.0 ms
64 octets from 212.140.212.13: icmp_seq=10 ttl=254 time=1082.2 ms
--- 212.140.212.13 ping statistics ---
13 packets transmitted, 10 packets received, 23% packet loss
round-trip min/avg/max = 1082.2/1525.8/2071.0 ms
And With
bash-2.05a$ ping 212.140.212.13
PING 212.140.212.13 (212.140.212.13): 56 octets data
64 octets from 212.140.212.13: icmp_seq=0 ttl=254 time=1213.0 ms
64 octets from 212.140.212.13: icmp_seq=1 ttl=254 time=423.4 ms
64 octets from 212.140.212.13: icmp_seq=2 ttl=254 time=70.4 ms
64 octets from 212.140.212.13: icmp_seq=3 ttl=254 time=257.0 ms
64 octets from 212.140.212.13: icmp_seq=4 ttl=254 time=608.9 ms
64 octets from 212.140.212.13: icmp_seq=5 ttl=254 time=398.9 ms
64 octets from 212.140.212.13: icmp_seq=6 ttl=254 time=62.2 ms
64 octets from 212.140.212.13: icmp_seq=7 ttl=254 time=70.2 ms
64 octets from 212.140.212.13: icmp_seq=8 ttl=254 time=90.3 ms
--- 212.140.212.13 ping statistics ---
9 packets transmitted, 9 packets received, 0% packet loss
round-trip min/avg/max = 62.2/354.9/1213.0 ms
So yeah, not too sad here. Although it did seem at times that wondershaper would reduce the download speed to 2K/sec. But web performance did seem to be normal with it's use.
Would be nicer to be able to run it on my smoothie so it applies to the family machine downstairs too.