Submitted by Robert (not verified) on Thu, 2007-05-10 04:16.
As a former Penguin Customer myself, I can completly understand where your comming from.
Actually what makes this funny is, I was actually ON server 131 for a brief time before packing up my service (although canaca.com is just as bad if not worse as penguin was)
I kept having issues with the php service on that server as well how ever it was not a specific user the process would just stop responding all together at random intervals and my entire site is driven by php and mysql.
I’m fairly certain they only give each of their VPS systems about 400 Mhz of processor time at most. I had setup a cronjob to report to me the actual server specs but quickly had my account suspended since apparently cat /proc/cpuinfo was a voilation of the terms of service. They quickly re-enabled my account
On that server specificly I had seen server loads hit 150 before they rebooted the server
Simalar Story
As a former Penguin Customer myself, I can completly understand where your comming from.
Actually what makes this funny is, I was actually ON server 131 for a brief time before packing up my service (although canaca.com is just as bad if not worse as penguin was)
I kept having issues with the php service on that server as well how ever it was not a specific user the process would just stop responding all together at random intervals and my entire site is driven by php and mysql.
I’m fairly certain they only give each of their VPS systems about 400 Mhz of processor time at most. I had setup a cronjob to report to me the actual server specs but quickly had my account suspended since apparently cat /proc/cpuinfo was a voilation of the terms of service. They quickly re-enabled my account
On that server specificly I had seen server loads hit 150 before they rebooted the server