here's a screenshot. i didn't include the table stuffs. <a href="http://skitch.com/thomasswift/xef3/twitter" rel="nofollow">http://skitch.com/thomasswift/xef3/twitter</a>
these queries are not optimised at all. first of all, every page gives of MySQL warnings...and second, there are alot of SELECT count(*)...instead of SELECT count(1). This may not seem like it would increase speed alot but given the number of users and the amount of times that query is executed, it will speed up twitter by a bit.
There are a few other things that i have noticed...they should really clean up their sql
Wish I'd taken a screenshot now.<p>It was basically a semi-transparent box in the top left of the screen which showed you the query as well as which DB served the data (for me they came from db007, and the friend data from some shards), and two links, one for a popdown box with info about the query, and another with the file trace infomation.<p>Quite intresting, shame they have removed it.
Seems like this was a mistake by twitter: <a href="http://getsatisfaction.com/twitter/topics/staging_twitter_com?utm_medium=widget&utm_source=widget_twitter" rel="nofollow">http://getsatisfaction.com/twitter/topics/staging_twitter_co...</a><p>Some profile pages are being linked to the staging server.