StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
8400999
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-12-06T13:54:15.903
FavoriteCount
0
LastActivityDate
2011-12-06T14:24:40.507
LastEditDate
2011-12-06T14:24:40.507
LastEditorUserId
910107
OwnerUserId
910107
ParentId
8400643
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
First, i will REALLY try to avoid your approach. I look at it as the "last chance" to avoid performance issues. You have alternatives (from hardware to software) on hard you can buy Fusion i/o or just an SSD drive (<a href="http://www.mysqlperformanceblog.com/2009/05/01/raid-vs-ssd-vs-fusionio/" rel="nofollow">Raid vs SSD vs FusionIO</a>). But, you can solve this using software and dont investing money at all. On your scenario you should use cache (i.e. <a href="http://memcached.org/" rel="nofollow">memcached</a>) if you aren't already using it. <a href="http://dev.mysql.com/doc/refman/5.1/en/partitioning.html" rel="nofollow">MySQL have partitioning</a>, its not the best choice in the world but, you can have some good performance increase. BUT, if you go with your idea, i suggest that you shard your data, using a value that split your data across tables more balanced. You can do something nasty like: create 50 tables like thread_0 to thread_49 And then (forumid % 50) so you land on one of this 50 tables. That way you avoid to create a table everytime you create a forum, and you avoid to have N tables. And the select with forum_id indexed will be very fast. Also you can have some sort of logic on the app to manage pagination, and avoid huge offsets. Good luck! PS: I add a blogpost on MysqlPerfomanceBlog <a href="http://www.mysqlperformanceblog.com/2009/08/06/why-you-dont-want-to-shard/" rel="nofollow">"Why you dont want to shard"</a>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POMySQL: duplicating data for more performance?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USGonza
UserOwnerUserId
1. USGonza
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POMySQL: duplicating data for more performance?
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.