Comments on: Mosso Pricing Update – Compute Cycles

By: badexperience

badexperience — Sat, 10 Jan 2009 00:54:52 +0000

Hello,
I had a bad experience with Mosso compute cycle pricing.
Everything else is stellar, the bandwidth, the ease, the price seems great … however mosso decided to take a big fat sh*t on the compute cycles.

This was for a site I made using hand written PHP/MySQL with very highly optimized code.
I wrote my own process watcher, etc. the compute cycles to me seem ‘fake’ because I did a quick test on a new site one test had heavy code, I ran that script 500 times, checked the compute cycles, next day I ran simple hello.htm page that contained “Hello” 500 times. the compute cycles were both the same, for every 50 hits = 1 compute cycle.

Very strange stuff, they don’t reveal anything about it other than generalities, your images etc … I set 100% of the images to s3.

I set php alternative caching to all the pages, set it very high to 5 days, still compute cycles ran through the roof.

So a warning, charging on something that is not verifiable is sketchy.

By: Danny

Danny — Wed, 13 Aug 2008 17:20:51 +0000

According to some Wiki I just looked at, a compute cycle consists of 2 parts: the instruction prefetch to load the instruction for execution and the execution of the instruction. However, Mosso is going beyond that by also examining disk IO so that database intensive work adds more to the compute cycles.
My partner and I have just setup a wesite for a client on Mosso’s hosting cloud and I am monitoring the cycles pretty closely since the website is rather database (MySql) intensive. Here is an example of the account usage:
Disk Usage: 12.8 MB
Bandwidth: 70.0 MB
Compute Cycles: 108
Requests: 11941
Some of that usage was on uncompiled .net code and had rapid cycle increases during a short period of time. We improved it by compiling the code but the cycles on compiled code are probably going to exceed what we are willing to accept once we find a reasonable alternative.

By: kumar

kumar — Tue, 12 Aug 2008 04:10:18 +0000

Can anyone explain what is compute cycle in mosso.com, how does one compute cycle is evaluated

By: Paul

Paul — Sat, 26 Jul 2008 00:08:45 +0000

Compute cycles is a terrible metric. I have one local website and one national website and I burned 8,000 compute cycles in 8 days. The allotment is 10,000 cycles/per standard account for 100 bucks. They estimate that I’ll be 283% over that. What is that $383 a month. I can get a dedicated box on Rackspace for that.

By: Shane

Shane — Mon, 23 Jun 2008 13:05:17 +0000

I’m new to Mosso. We put up a Magento (online store) based site and we’ve maxed out our compute cycles for the sites standard package by manually adding 300 product. We haven’t even launched the store yet.

By: Scott

Scott — Thu, 15 May 2008 21:20:08 +0000

I am also a Mosso customer and I have to say I couldn’t be more happy that they are changing their metric. This is a good move on Moss’s part. They listen to its users and reacted accordingly.

This new model goes along the same lines that Media Temple already have going. So it’s nothing new. It’s seems to be a proven metric that works and people can work with.

Cheers.