1996 was my first shared hosting. 96-97 was OK, but I had a project for a client that got shut down after a few days. It was a small ecommerce project, and we got shut down for 'resource abuse' - CPU was spiking and network was going crazy. Had a week of back and forth emails and I think phone with their 'support.
They were poking through my code, bitching that I was doing "select *" queries ("those are inefficient" they kept arguing). After a week we were reinstated - turns out there was someone else running spambot on another hosting account on the same server. But... we were "ecommerce" so obviously must have been the root cause of a spiked CPU. I vowed at that point to not use shared hosting again, and haven't since 1998.
It's been nicer with cheap VPSs over the last few years - easier to get clients set up with their 'own' servers. I know that VPSs are shared as well, and I've seen issues where one VPS abused resources to the point where it affected mine, but that's been pretty rare (2x in the past 5 years I can think of), and it's always easier for people to track down, isolate and resolve.
Also, it was one anecdote point, and was 15 years ago, and was just 'bad service' but life is too short to try to be putting projects as risk to save a few bucks. Projects/sites generally have enough troubles - dealing with shared hosting is just one more thing that can go wrong, imo.
Sorry for the late reply. Actually I've been running leased bare metal servers for most of the time. In the last couple years I've had some clients and projects on linode and digital ocean, but still have bare metal servers for most other stuff.
I haven't knowingly used virtuozzo for anything so I can't say. Most VPS I've had have been xen-based, but the hardware behind it seems to make more of a difference. I've got two virtualized xen projects right now, and same code on seemingly same virtualized hardware specs still yield pretty different results on some tests.
They were poking through my code, bitching that I was doing "select *" queries ("those are inefficient" they kept arguing). After a week we were reinstated - turns out there was someone else running spambot on another hosting account on the same server. But... we were "ecommerce" so obviously must have been the root cause of a spiked CPU. I vowed at that point to not use shared hosting again, and haven't since 1998.
It's been nicer with cheap VPSs over the last few years - easier to get clients set up with their 'own' servers. I know that VPSs are shared as well, and I've seen issues where one VPS abused resources to the point where it affected mine, but that's been pretty rare (2x in the past 5 years I can think of), and it's always easier for people to track down, isolate and resolve.
Also, it was one anecdote point, and was 15 years ago, and was just 'bad service' but life is too short to try to be putting projects as risk to save a few bucks. Projects/sites generally have enough troubles - dealing with shared hosting is just one more thing that can go wrong, imo.