Reads for twitter are the main scaling issue not writes. Try doing 6900 in 578 seconds while doing 50k+ reads/second :)
On Sun, Jun 10, 2012 at 11:44 AM, Peter Morris <[email protected]> wrote: > Twitter blog claims a record of 6,939 tweets in 1 second - this was 4 > seconds after midnight in Japan on New Year’s Day. > > I decided to run a test, the steps to insert a row would be 3 selects > + 1 insert (because of the data structure involved) - I managed 6900 > in 578 seconds. > > Obviously I am not expecting Twitter-like load handling on my > development laptop, but what tricks are involved in getting this kind > of performance and would NH + SQL Server be a bad choice for > implementing a similar service? > > > Pete > > -- > You received this message because you are subscribed to the Google Groups > "nhusers" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/nhusers?hl=en. > -- Le doute n'est pas une condition agréable, mais la certitude est absurde. -- You received this message because you are subscribed to the Google Groups "nhusers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/nhusers?hl=en.
