jeeze, compiling haskell packages takes nearly 1 gig of ram on its own.  I may have to bump the RAM on my VPS up, this swapping is killing me (and the disk, I'm sure)
up_the_irons: would running iperf tests with a vps as the iperf server have a negative effect upon your architecture?
I expect that'll depend on what's on the other end of the test.
:P
*nod* i could push about 300 mbps right now and a gig in the near future.  vps would be a convenient for testing but i don't want to do that if it's going to have a detrimental effect on the whole environment.
i'm not sure how much bandwidth garry has and he might not want to go into specifics in a public forum. i should probably just email him instead.
cat /proc/cpuinfo | grep processor | wc -l -> 1 :(
so add a core
I would suspect that bursting a gig to a vps, even if you could actually push that much given whatever other overhead/bottlenecks there are, would have a negative effect yes.
well, sustaining. Shrug.
VPS host NICs are limited to 100mbps  so you'll never get over that despite gig uplinks. And saturating that 100 meg link wouldn't be nice for the other customers. But of course only up_the_irons can make the call.
jlgaddis that would be considered DoS in most respects
using iperf in  manner that would saturate lnks that is
+i
Well, he is just asking. :)
mhoran: *nod* that's why i asked
at high speeds, ndt is better anyway, but iperf is quick and easy
reardencode: Which packages? Some packages with e.g. fun deps or TH take forever.
mike-burns: I noticed on the kate highlighting library took forever and up to 1gb ram