And yet the status page says everything’s fine.

If you have 3 webservers running apache, and each apache process can potentially create one connection to memcached, you calculate this by your MaxClients setting. IE; the maximum potential apache processes that can be running at a time.

If that’s set to 30, then you have 30 3 == 90 possible connections. Might as well set -c to 4096 to be safe ;)

Between this and the Drizzle team leaving you can connect the dots to how Oracle is going to treat MySQL.

Its not a coincidence that in both cases the company to pickup the talent was a cloud hosting one.

and thats just the last few weeks

also, check this out, its got to be a kidney harvesting scam or something
IT Team Lead (Bermuda)

Then this morning Vito passed me this: High Performance Computing Hits the Cloud
Which also led me here: New Amazon EC2 Instance Type – The Cluster Compute Instance

And for a few minutes there I thought they’d finally done it and I was wrong.

But alas, no, the “cluster compute instance” which appears to be one-half of a quad-socket/quad-7200rpm-drive server is offering you just that. 2x 7200rpm sata drives. Thats maybe 150 good random IOPS, not even close :(

You could string a bunch of them together in some kind of crazy LVM on iSCSI setup but you’d probably still only wind up with something in the ~600 IOPS family you can already get with almost-as-convoluted EBS setups.

Seems like there’s two ways around this currently. Keeping stuff in-house (well, colo) so you can scale up the hardware, or having your developers rewrite everything to not depend on a single MySQL-write-master so tightly. I always bet against the option that requires devs to redo stuff.

this post is over a year old but I had never heard of it before
http://developer.yahoo.net/blog/archives/2009/06/sherpa.html

looks like they’ve been busy in the meantime:
http://developer.yahoo.net/blog/archives/2010/06/sherpa_update.html

no talk of plans to opensource it or even make it available as a service though

oops

Looks like the same basic premise, design, and pricing.     This is awesome.  Now you can solve the “what if s3 is down/slow” question with a redundant vendor instead of inhouse infrastructure.

Choice quotes:

In the days after an oil well spun out of control in the Gulf of Mexico, BP engineers tried to activate a huge piece of underwater safety equipment but failed because the device had been so altered that diagrams BP got from the equipment’s owner didn’t match the supposedly failsafe device’s configuration
…

“When they investigated why their attempts failed to activate the bore ram,” Stupak said of BP engineers, “they learned that the device had been modified. A useless test ram _ not the variable bore ram _ had been connected to the socket that was supposed to activate the variable bore ram.”

“An entire day’s worth of precious time had been spent engaging rams that closed the wrong way.”

clearly not the cause, but there’s a DR lesson here for sure.