Results 1 to 25 of 53
Threaded View
-
04-25-2013, 12:23 PM #1Junior Guru Wannabe
- Join Date
- Dec 2009
- Posts
- 60
StyleXnetworks review - Terrible.
Hello,
I rarely post negative reviews because with the amount of competition I can just cancel and go elsewhere. But StyleXNetwork is so terrible I just had to speak up.
I don't just run benchmarks all day looking for problems. I use this VPS for a few things and I notice problems with performance which makes me investigate.
I have been a customer since June of 2012 (I paid for 6 months and renewed it once that is why I have not cancelled yet)
------
Invoice 201206XXX
Date of Invoice 21/06/2012
Due Date 21/06/2012
-------
The Plan:
Single Core
256MB of memory
10GB Disk (1GB of which is forced as swap which is fine though would be nice to use a bit less for swap)
The problems:
-Poor Disk IO. This is the biggest problem. 10-20 IOPS and 5-50MB/s disk write (50 is fine if it was consistent)
-Server randomly gets shutdown and does not come back up unless you boot it up from within the panel.
-Support (see below)
-Network unstable. Month by Month this VPS sits at 95%-96% uptime according to both pingdom and StatusCake.
Support:
Useless. You open a ticket and they blame you right away.
For the VPS being shut down all the time they claimed I hit reboot using the control panel and that it got "locked" I have never rebooted this VPS since I got it except from within the vps itself using the reboot command. I tried explaining that to them and they come right back saying the exact same thing. It is like a robot is answering your tickets using a keyword search in your ticket.
As for the performance problems with IO I have been told various stories. From the fact the SAN is junk and they are replacing it to the fact that it is a problem with my VPS. Sometimes they will provide the same test from the node showing decent results and I try it and it is fine for a while. So obviously they fixed it but instead of just saying it they pretend like nothing happened.
Some Example tests done at random times:
./ioping -c 10 .
4096 bytes from . (ext3 /dev/xvda1): request=1 time=0.3 ms
4096 bytes from . (ext3 /dev/xvda1): request=2 time=32.5 ms
4096 bytes from . (ext3 /dev/xvda1): request=3 time=50.5 ms
4096 bytes from . (ext3 /dev/xvda1): request=4 time=0.5 ms
4096 bytes from . (ext3 /dev/xvda1): request=5 time=0.0 ms
4096 bytes from . (ext3 /dev/xvda1): request=6 time=0.5 ms
4096 bytes from . (ext3 /dev/xvda1): request=7 time=0.4 ms
4096 bytes from . (ext3 /dev/xvda1): request=8 time=610.7 ms
4096 bytes from . (ext3 /dev/xvda1): request=9 time=50.7 ms
4096 bytes from . (ext3 /dev/xvda1): request=10 time=0.7 ms
--- . (ext3 /dev/xvda1) ioping statistics ---
10 requests completed in 9748.7 ms, 13 iops, 0.1 mb/s
min/avg/max/mdev = 0.0/74.7/610.7/179.8 ms
./ioping -c 10 .
4096 bytes from . (ext3 /dev/xvda1): request=1 time=0.3 ms
4096 bytes from . (ext3 /dev/xvda1): request=2 time=0.5 ms
4096 bytes from . (ext3 /dev/xvda1): request=3 time=2.8 ms
4096 bytes from . (ext3 /dev/xvda1): request=4 time=433.6 ms
4096 bytes from . (ext3 /dev/xvda1): request=5 time=0.5 ms
4096 bytes from . (ext3 /dev/xvda1): request=6 time=0.4 ms
4096 bytes from . (ext3 /dev/xvda1): request=7 time=1.1 ms
4096 bytes from . (ext3 /dev/xvda1): request=8 time=0.4 ms
4096 bytes from . (ext3 /dev/xvda1): request=9 time=0.4 ms
4096 bytes from . (ext3 /dev/xvda1): request=10 time=0.9 ms
--- . (ext3 /dev/xvda1) ioping statistics ---
10 requests completed in 9442.7 ms, 23 iops, 0.1 mb/s
min/avg/max/mdev = 0.3/44.1/433.6/129.8 ms
Conclusion: Poorly managed, Poor support, VERY slow nodes and SAN. I will never use them again, I would suggest you go with a 1 month test run before putting anything into production.
I provided my root password to them and they said they would escalate to an engineer. They closed the ticket. When I reopened the ticket here is the response I received:
-------------------
The ticket get closed automatically we are sorry for that ,
however regarding your IO problem your package is limited resources and if there is a load you automatically get throttled on CPU which cause the IO problem , We highly recommend that you upgrade to one of our normal packages,
-------------------
My cpu usage is 0.00 to 0.07 so I can't see this being a factor.
I am cancelling and moving on. I just wanted to post this here in the hopes no one else falls for this junk.
Similar Threads
-
stylexnetworks 1 Month Review
By chatbox in forum Web HostingReplies: 2Last Post: 03-04-2013, 01:56 PM -
StyleXnetworks.com review - AVOID
By KeithThomson in forum Web HostingReplies: 5Last Post: 02-07-2013, 03:55 PM -
VPSLatch (Terrible Review)
By Grumps in forum VPS HostingReplies: 41Last Post: 01-24-2011, 08:23 PM -
Just Edge NY (REVIEW :: Terrible)
By PrimeTimeHosting in forum Dedicated ServerReplies: 10Last Post: 09-03-2008, 11:59 AM -
dot5hosting review - TERRIBLE
By mikexx2020 in forum Web HostingReplies: 7Last Post: 03-17-2007, 07:56 PM