It takes 113 servers to run Google Calendar
14th Nov 2006, 02:39 GMT
Thanks to Tony Ruscoe who did some digging around Google Calendar, we have a "changes" file meant for internal eyes only. The file he posts is mirrored since Google removed the changes file soon after it was discovered."Logs estimate: I count about 317 records/day/server. I see on average about 1.4 clienterror-count entries/record so therefore 20 + 8 + 2 * 8 (1.4) ~ 50.4 bytes/record. Hence 15.9k bytes/day/server * 113 servers ~ 1.8Mb/day extra to temp logs. This is uncompressed."In addition to the changes file, he also found a button that will let you search "public events" and some strange links at the top labelled "Google Internal IP Visible Info:".
It takes 113 servers to run Google Calendar related news:
- It Takes 113 Servers To Run Google Calendar — digg
- Google Showing "Internal IP" Info — Google Blogoscoped
- Sync your Google Calendar with your cell phone — Lifehacker
- Google Spiffs Up Private-Label Tools (NewsFactor) — Yahoo! News: Internet News
- Google Spiffs Up Private-Label Tools — NewsFactor Network
- Is Google evil? — Hack In The Box
- Google Takes Out Ajax Spreadsheet iRows — TechCrunch
- Google Wants To Start Up Your Domain — Internet Insider Reports from WebProNews
- Start your day off right — Official Google Blog
- Google Acquires JotSpot — Search Engine Optimization, Google Optimization - RSS Feeds
Latest news from ZDNet Blogs:
- A global avalanche
- Guess what devices these celebs are using
- Web 3.0: What will Mike Arrington do now?
- Q&A with Tim Bray
- As Stallman looks on, Sun frees Java under the GPL
- The ripple effect of a GPL'd Java will reach far and wide
- What should Microsoft do, now that Java is GPL'd?
- Green: Sun may release Solaris under GPL next
- Who is an identity-based NAC vendor?
- What a free Java means for Rich Internet Applications