Kevin Rose Load Tests Gmail
SishGupta writes "Load Testing Gmail - fillmybox@gmail.com
A few weeks ago, Kevin Rose of the The Screen Savers decided to load test Google's new email service, Gmail. He asked everyone to email him their favourite 5MB attachments to 'fillmybox@gmail.com.'
The test Gmail account is now 102% maxed out.
You can read about the test and the results at Kevin Rose.com (his weblog)."
I hope gmail scales better that that... Anyone has a link?
Write boring code, not shiny code!
The limit as stated on the quota page is 1000MB, not 1GB. That's why he's at 102%.
It is arguable whether 1GB is 10^9 or 2^30 bytes, however, the strictest and most current definition of 1 GB is 10^9 bytes.
"You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
Actually 1GiB is equal to 1024MiB while 1GB is equal to 1000MB
Yes I was watching when it happened. I'm sure striger or whatever his name is had a talk with him afterwards.
Kev, Sarah, you guys need to be a little less obvious about your love life on air, either that or rig the playboy contest so sarah wins. that thing still going on?
If you have the clip e-mail me at admin (at) uneasysilence.com I would love to host it
_dan
http://www.uneasysilence.com
Actually, Hotmail allows you to fill about 110% of your capacity before it actually starts to bounce messages. Right now it's a measly 2 MB, but it should be increased to 250 MB in the next few weeks.
While this is funny and all, I'll explain.
Google offers 1 GB, or 1000 MB, of space. They do this as to not confuse non-tech folk. When you reach 1000 megs, it's 100% full. When you reach the actual limit of 1024 megs, it's 102% full.
Oh, and back when yahoo had a 4 meg limit, my throway's account would gather up spam and it would stop me at 5 megs, or 125% of the limit. No idea what happens now that it's 100 megs.
Etiquette is etiquette. He kills his mother but he can't wear grey trousers.
What he thinks is most likely a bunch of rot.
Decompress a gig on the fly when you login. Please... Do me a lemon.
The real trick is in the routing for this type of application. When mail is delivered it is switched to a bank of servers which deal with your account (and many others obviously). The messages are indexed and stored.
When you login there will be a range of load balanced servers routing your read requests back to that same bank of storage from the frontline web servers.
Limit management is either done in the application logic, or in the database engine. Under load, with simultaneous receipts it's easy to see why you could go over 100% of storage. It's either that or you have to serialize the delivery per user which would suck and be harder.
It's not a hard concept, but it is tricky to get right in implementation. This is what Google does best though.
Here's the segment from g4techtv captured by me: http://www.members.shaw.ca/fog_dogg_69/fillmybox.w mv
The hard drive manufacturers and the computer manufacturers have been doing this for years, and the average consumer has not noticed. Google is just going with the flow by saying 1 GB = 1000 MB.
http://it.slashdot.org/comments.pl?sid=115848&cid= 9808280
I believe 4 degrees C was chosen as that is the temperature at which water is most dense. Not a number picked out of nowhere.
According to the National Institute of Standards and Technology, you're ... right!
There's a link showing binary multiples here
http://www.members.shaw.ca/fog_dogg_69/fillmybox.w mv
Correction to Story:
"K" is the unit of temperature, the Kelvin.
"k" is the abbreviation for "kilo", 1,000.
The IEC isn't universal? Perhaps, but neither is the ISO. :-) Further, IIRC, the IEC wrote the initial SI standard, and it may have slipped your notice, but we're talking about computers, which is definetly an elec eng topic - and as you yourself state, the IEC is definetly a relevant body for elec eng.
:-)
:-) (And lets not even talk about floppy disks, where 1.44M = 2^10 * 10^3 bytes...)
Further, the IEEE (a very relevent body for this topic) has decided that kilo, mega, etc. always and everywhere refer to their base-10 meanings - even if you're talking about bits and bytes, if you are referring to the base-2 meaning, you must explicitly state this on a case by case basis.
Further, the IEC standard has recently been submitted to the IEEE (and also to the ISO, although it's not really their area), and is currently being tested as a "trial-use standard" by the IEEE, and is expected to be officially adopted by it sometime next year.
There is no standard anywhere which defines kilo as 2^10. Kilo, as an SI prefix, is defined to be 10^3. The only prefix defined as 2^10 is Kibi. Well, as far as I'm aware, anyhow. But since the ISO, IEEE, and IEC (which in turn in an umbrella group for the various national standards bodies like ANSI, etc.) all agree on what kilo does and does not mean (and the only groups with an opinion agree on Kibi, I think we're running out of standards groups. If you know of a standard that defines kilo as 2^10, please cite.
None of which, of course, changes the fact that Joe User uses "megabyte" all the time to refer to 1,048,576 bytes, but since hard disk makers have already switched to calling 10^9 bytes a terabyte, I don't see how using the base-2 prefixes can increase the anger and frustration.
If you want to be precise when describing the number of bits, use the International Electrotechnical Commission's recommendations for binary quantities. The names are a combination of the multiple and the letters "bi" for binary, eg. kibi, mebi, gibi. The wiki page is here, and I've included the relevant table below:
Name Abbr Factor
kibi Ki 2^10 = 1024
mebi Mi 2^20 = 1 048 576
gibi Gi 2^30 = 1 073 741 824
tebi Ti 2^40 = 1 099 511 627 776
pebi Pi 2^50 = 1 125 899 906 842 624
exbi Ei 2^60 = 1 152 921 504 606 846 976
Already done.
http://en.wikipedia.org/wiki/Mebibyte
Unfortunately, this means the standard prefix actually changes for the more "engineering" of the two sizes, and I don't think it has a lot of acceptance.
1 KiB = 2^10 B
1 MiB = 2^20 B
1 GiB = 2^30 B
etc.
They are rather fun to say though.
Not old news. Your friend simply filled his Gmail account. That's no big deal. Your friend even said "nothing unexpected happened". What makes Kevin Rose's news interesting is that continued traffic on an account can lock out the owner. That's a significant bug in that one can launch a denial of service attack on a Gmail user.
Slashdot monitor for your Mozilla sidebar or Active Desktop.