Eric Hodel wrote:
> On Sep 25, 2007, at 07:22 , M. Edward (Ed) Borasky wrote:
>> Ruby Maniac wrote:
>>> Just buy a bunch of Quad Core Opterons and get over it !
>>>
>>> If you don't think Ruby is scalable just check with the folks at
>>> Twitter - they have been successfully using Ruby for some time now -
>>> all they had to do was buy a ton of compute gear and life is good !
>>
>> If Twitter is a for-profit venture, I'd be very surprised if usable
>> details about how they plan and manage load, scalability and capacity
>> are available without an NDA. This is something we performance engineers
>> consider "The Family Jewels", although perhaps curious folk in other
>> disciplines wonder what the fuss is all about. :)
> 
> These things are less secret than you think.  Twitter's solutions to 
> scaling issues are going to be inappropriate to your scaling issues.  
> Knowing the details won't help you, knowing the techniques will.
> 
The Twitter folks have been very forthcoming about the trials and 
tribulations of scaling up their system to meet demand.  All sorts of 
details regarding language tweaks, hardware changes and DB schema 
improvements were all available to the public.

Now, I'm sure not everything was made public, but they have been more 
than transparent about their scalability issues.