Geek Answers Handbook

Which is more efficient: one long single table or a distributed table? and why?

This question is about performance, and I would appreciate it if the answers were specific to the case I am providing.

Which is more suitable for performance?

  • creating a table with too many fields
  • creating more than one table and distributing similar fields to them

CASE: Advanced CMS Web Module

Sample 1: long but one table

cms
-----------------------------------------------
Id
Title
Description
Images
Order
Status
Publish
meta_keywords
meta_description
meta_author

Cleary, most open source CMS, such as joomla, use the above template. But I think this template kills the spirit of RDBMS . We can easily split the content, configuration, and meta of a specific article into different tables. As below

Sample 2: Many but related tables

Cms_content         cms_meta        cms_configuration
---------------------------------------------------------------------------
Id                  id              id          
Title               content_id      content_id
Description         keywords        status
Content             description     order
Images              author          publish

:

? , , ?

+5
2

( ), , :

  • SQL JOIN s

, :

  • (, , ..)
+5

, "" - "", - RDBMS .

  • : , , ..
  • /: , .
  • : (, memcached).

, - . 100 ​​ , . 5M , - 10 10- ( !) - , .

, , . DBA. ( )

+2

More articles:


All Articles