so, uh, how bad should disk performance on my vps be?
ls takes ~2s to list an empty directory.
dd /dev/zero to a file writes at ~1MB/s.
jdoe: ARP is probably one of the best disk I/O vps's I've ever used.  So,  if you're seeing that kind of issue,  email support@  it's likely an abusive client, or a misconfiguration.
it's a stock debian install and the machine is otherwise pretty much idle.
right.  I understand that.  but it's possible another client on your VPS is causing a problem.   I'd get an email out to support@ so they can investigate.
21,327,698 bytes/sec
on my OpenBSD vm
I switched from obsd because the performance was abysmal, was hoping pv drivers on linux would help.
apparently that wasn't the issue, or wasn't the only issue.
jdoe: did you let ARP know you were switching from BSD to linux?  I know there are a couple things they can change to make linux run a little better in the VPS.
jpalmer: well I asked them to change the media for me when I did, does that count? ;)
well,  I'd doubt they went and looked up your old media.  so, I think I'd specifically ask them to do any linux optimizations they have.  not sure if downtime would be required for it though.
21mb/s write is not bad for a VM, especially in a shared environment
vcs: agreed
thats odd you would only get 1/s
i would contact support
I'm getting 2.5MB/s on kvr05 and 53MB/s on kvr16
I'll bet the lower the kvr number, the lower your write speed.
how are you guys measuring disk speeds?
i'll do it on kvr04 for comparison
jlgaddis: dd if=/dev/zero of=~/test.txt is what I did.
Just make sure not to let it run for too long, 20 seconds gets you a gig at my better speed.
didn't specify bs or count or anything?
Nope
ok
Just let the OS run as it wanted to, would give more reliable results I'd assume.
93209088 bytes (93 MB) copied, 18.3983 s, 5.1 MB/s
my vps isn't exactly "idle", though, so that's probably not a fair comparison
Neither is my first one
I'm going to assume that up_the_irons does some type of firewalling, or slowing.
just ssh, afaik
> 10 syn's per minute to 22/tcp and the ip is blocked for 60 seconds, if memory serves
i know it's something like that... otherwise there's no filtering
I have my own pf rules.. more than 5 connects in 30 seconds, you're blocked bitch lol
jlgaddis: you are correct
(about ssh)
no other filtering
so happy I don't run ssh on 22 anywhere :)
far less noise in the logs
yep
On one box, I have it on 443
handy when you need to tunnel out of an agressive firewall
use the https proxy instead :)
I use sshguard
don't need that if you stay away from 22
there's really no point in putting sshd on 22 these days