The email sent will contain a link to this article, the article title, and an article excerpt (if available). For security reasons, your IP address will also be included in the sent email.
It's HighScalability Time:
- 4 Trillion Objects: Windows Azure Storage
- Quotable Quotes:
- @benjchristensen: “What if we could make the data dense and cheap instead of sparse and expensive?” James Gosling @liquidrinc
- @sinetpd360: People trying new things and sharing is what helps create scalability. Jim Rickabaugh #siis2012
- @rbranson: This h1.4xlarge running 160GB PostgreSQL database pushing ~17,200 index scan rows/sec. r_await is 0.79ms, box is 92% idle.
- @sturadnidge: faster net and disk greatly reduces repair time and impact so we can load up the instances with far more dat
- With Amazon announcing 2TB SSD instances the age of SSD has almost arrived. Netflix has already published a very thorough post on the wonderfulness of SSD for both performance and taming the long latency tail. They see 100K IOPS or 1GByte/sec on a untuned system. Netflix projects: The hi1.4xlarge configuration is about half the system cost for the same throughput; The mean read request latency was reduced from 10ms to 2.2ms; The 99th percentile request latency was reduced from 65ms to 10ms. Vertical scaling gets a huge boost as the bottleneck will likely move from IO to CPU again. Software will need a rewrite to be SSD optimized. Think about removing caching layers. Think reserved instances to bring down the cost. Think putting hot data into SSDs. We'll also see pressure to fix TCP interrupt bottlenecks and IRQ affinity problems.
Don't miss all that the Internet has to say on Scalability, click below and become eventually consistent with all scalability knowledge...
Return to Article