Re: Performance (lots of tables / databases...)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

the first choice is probably the best for you. When you think about second solution, it will be a nightmare when you have 1000+ databases and have to administrate them from one central system (if you're about to do it like this). The third solution looks little complicated to me - have one DB for comments, one for items etc.

But you can do it also in one database and six tables. Make one table 'blogs' where the blogs names and ids will be stored. Then you can just add one more field 'blog_id' to every table and identify items, categories, whatever on this. However in your situation (1000+ blogs) it may be not the best solution.


Martin Zvarík napsal(a):
Hi,
I am working on a blog system and I am currently thinking of what would be the best DB approach.

I have read lots about wordpress and other blog's optimizations and DB structure, but I have not found any mention of having separate database for each blog/user.

So, my question is, which one is performance better (talking about 1000 blogs):

a) 1000 blogs * 5 (let's say we will have tables like comments, post... for each blog) = 5000 tables in one database
... this is Wordpress default

b) 1000 databases (for each blog) each having 5 tables

c) 5 databases by 1000 tables - in this case, won't this be an issue when SELECTing like this: [db_comments].testblog, [db_posts].testblog ?


Is that a controversial topic? :-/

Thanks for ideas,
Martin


[Index of Archives]     [PHP Home]     [PHP Users]     [Postgresql Discussion]     [Kernel Newbies]     [Postgresql]     [Yosemite News]

  Powered by Linux