New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
16384+0 records in
16384+0 records out
1073741824 bytes (1.1 GB) copied, 1.27579 s, 842 MB/s
Unbelievable ...
Not really, on SSD node.
@Nick_A can comment on the single homed aspect. See the new provider coming this week it seems.
Tinet is peered massively and in Atlanta I do believe. Far from my favorite upstream as through peering they don't seem to be dumping folks off but long hauling them, which is hit or miss on latency and direction.
I get 27ms to FIOS connection in the Northeast from Ramnode.
I get a similar result with my cached SSD node. RamNode is tops.
He's on SSD-cached according to his recent PM thanking me.
Concerning the "fake review" blahblah: I have tested dozens and dozens of providers during the last years and nearly every provider that is regulary featured on LEB and my #1 choice for Europe is Prometeus while the #1 for the East of the USA is RamNode. Persistent and good to great performance over months.
I also love BuyVM for their service and general "No Shit" attitude, but they are still my #2 for the USA.
This pretty much is the same idea of my. Prometeus for EU is awesome while Ramnode is definitly number 1 for east us. I currently got a vps with Buyvm in Vegas but it feels slow because I'm in the EU.
I would also like to mention KnownHost/RocketVPS as being fantastic hosts, but they are catering another clientele in another price segment.
Thanks guys for the appreciation.
Sorry Nick for invading the pitch (thread) :-)
o_O
He's just jealous for not having his own thread. :P
/jk
Thanks guys!
That ping seems fine to me. Is it not?
Tinet is a very good bandwidth provider. Solid network, inexpensive, well-peered...
I'm getting problems at this node on the way from Verizon FIOS in northeast to RamNode in Atlanta: tinet-gw.customer.alter.net
Google search reveals that many other people are having the same problem (that is, many other people with Verizon FIOS, not RamNode).
Tinet is well peered. But their ability to route in proper direction lately is off in bunch of places. Plus their peering might be in say Ashburn. Meaning start in Atlanta intending on end point of say Atlanta and end up going up to Ashburn and back.
Seeing that in multiple locations with Tinet. Sloppy routing or lack of peering. Neither matters to me. I hate asking for route cleanups all the time.
27ms is actually very good. Peering to Verizon is great. FIOS in general is a rocking network in all ways (my experience).
Not getting 27 ms, more like 100 ms - 200 ms and very unstable (according to traceroute / ping that people sent me). I ended up setting up a proxy server in northeast that connects client to the RamNode server (which didn't have the routing problem associated with Verizon FIOS), and that actually solved the problem.
@pernnate, try Tinet's looking glass back to your IP:
http://www.ip.tiscali.net/lg/
Atlanta pop is in the list.
Route might not be the same both ways, but compare.
@perennate - http://lg.nlayer.net/ in case you're interested.
root@server:~# dd if=/dev/zero of=test bs=64k count=16k conv=fdatasync
16384+0 records in
16384+0 records out
1073741824 bytes (1.1 GB) copied, 3.78546 s, 284 MB/s
root@server:~#
Is that normal? Get more than double with DO.
@Ishaq - I need to know what node that's on to be able to answer that.
@Ishaq virtio selected under Manage > Settings > Disk Driver in SolusVM?
He's on OpenVZ
@Nick_A
VZSSD9
I'm looking at it now @Ishaq. The drives are all in great condition, no errors on the RAID card, and IOPS are all normal. But the DD is extremely slow for some reason.
Only on RamNode :P
ioping -RD .
--- . (ext4 /dev/sda3) ioping statistics ---
28549 requests completed in 3000.0 ms, 22055 iops, 86.2 mb/s
min/avg/max/mdev = 0.0/0.0/18.5/0.1 ms
ioping -RL .
--- . (ext4 /dev/sda3) ioping statistics ---
10849 requests completed in 3000.2 ms, 5185 iops, 1296.3 mb/s
min/avg/max/mdev = 0.1/0.2/2.3/0.1 ms
ioping -RC .
--- . (ext4 /dev/sda3) ioping statistics ---
53767 requests completed in 3000.0 ms, 684851 iops, 2675.2 mb/s
min/avg/max/mdev = 0.0/0.0/2.4/0.0 ms
ioping -c 10 .
4096 bytes from . (ext4 /dev/sda3): request=1 time=0.1 ms
4096 bytes from . (ext4 /dev/sda3): request=2 time=0.1 ms
4096 bytes from . (ext4 /dev/sda3): request=3 time=0.1 ms
4096 bytes from . (ext4 /dev/sda3): request=4 time=0.1 ms
4096 bytes from . (ext4 /dev/sda3): request=5 time=0.1 ms
4096 bytes from . (ext4 /dev/sda3): request=6 time=0.1 ms
4096 bytes from . (ext4 /dev/sda3): request=7 time=0.1 ms
4096 bytes from . (ext4 /dev/sda3): request=8 time=0.1 ms
4096 bytes from . (ext4 /dev/sda3): request=9 time=0.1 ms
4096 bytes from . (ext4 /dev/sda3): request=10 time=0.1 ms
--- . (ext4 /dev/sda3) ioping statistics ---
10 requests completed in 9001.4 ms, 15949 iops, 62.3 mb/s
min/avg/max/mdev = 0.1/0.1/0.1/0.0 ms
./dd.sh
16384+0 records in
16384+0 records out
1073741824 bytes (1.1 GB) copied, 3.82655 s, 281 MB/s
Updated the kernel and scheduled a reboot.
@Nick_A
Just wondering if I'm already getting a DD of 700MB/s on the cached SSD whats the benefit of getting pure SSD? the difference in drive space is huge 5Gb for pure SSD and 30GB on cached SSD?
Also is the E5 CPU only offered on the cached KVM node?
I only get 500MB/s DD test on my cached SSD, is that normal or should I ticket?