|
|
Rank: Newbie
Joined: 1/7/2008
Posts: 16
|
Hi,
I m developing multiple user blog - so each user can write to his own blog, comment others and so on. I planned to do it using umbraco nodes - each blog is a node and comments are the childs. But i started doubting - if such structure will cause low site perfomance in case of the huge user visiting. If umbraco will work correctly with a huge nodes amount? So what i should do - continue working with nodes or create for blogs separate db tables with DAL layer. Can anyone give a suggestions?
Tnx.
|
|
Rank: Umbracoholic
Joined: 9/8/2006
Posts: 1,408
Location: KY, USA
|
There is an upper-limit to nodes in umbraco (something like 200,000). If you're going to go beyond that you'll want store data in an external table/database and use a user control or xslt extension to transfer the data. By way of reference, the umbraco forum currently has about 22,000 nodes in it. No problems there with performance. cheers, doug.
MVP 2007-2009 - Official Umbraco Trainer for North America - Percipient Studios
|
|
Rank: Newbie
Joined: 1/7/2008
Posts: 16
|
So, if we will have 20 000 registered users and for example 20% of them will use blog service every day - they will post 4 000 posts (and for example 2 000 comments). In this case we will have died portal in a month. Hmm - this is really not good perfomance.
Tnx for replying.
|
|
Rank: Aficionado
Joined: 7/19/2006
Posts: 148
Location: aalleren, Denmark
|
You should put all these numbers into perspective. Umbraco has a upper limit on 200.000 nodes, which is 200.000 fully managed, chached, versioned, templated nodes, so consider where on your site you would need all that functionality. I would personally store blogs and blog posts in umbraco, and then all comments in a seperate table. It's really straight-forward to integrate external data in umbraco's xslt editor. If you after 1-2 years hit performance issues with storing 200.000 blog posts in umbraco, then do a migration to store those in a optimised table as well, then you'll only have the individual blog nodes stored in umbraco. So you can do it, but if you are going to build a platform that will only be a blogging tool, and nothing else, and need out of this world scalability, then you probably shouldn't go with a 100% umbraco based solution, either using external ways to store all that data, or use a blogging focused system instead.
Umbracian Personal blog: Objects.dk
|
|
Rank: Newbie
Joined: 1/7/2008
Posts: 16
|
pph wrote:You should put all these numbers into perspective.
Umbraco has a upper limit on 200.000 nodes, which is 200.000 fully managed, chached, versioned, templated nodes, so consider where on your site you would need all that functionality.
I would personally store blogs and blog posts in umbraco, and then all comments in a seperate table. It's really straight-forward to integrate external data in umbraco's xslt editor.
If you after 1-2 years hit performance issues with storing 200.000 blog posts in umbraco, then do a migration to store those in a optimised table as well, then you'll only have the individual blog nodes stored in umbraco.
So you can do it, but if you are going to build a platform that will only be a blogging tool, and nothing else, and need out of this world scalability, then you probably shouldn't go with a 100% umbraco based solution, either using external ways to store all that data, or use a blogging focused system instead.
Blogging tool is only one of the available services - there are additional services which have the the same architecture(multiple user nodes). Thats why a i m started thinking abt performance. So will try approach, when node is an individual blog - other functionality will cover with user controls and separate db tables. Tnx for advice.
|
|
|
Guest |