We have multilingual site on v6.1.6 it has 50 language instances and roughly 9000 nodes in total so maybe about 150 nodes per instance.
The tree takes a bit of time to load. Main thing is the more properties you have the more of an impact on performance. This is for 6.1.6 v7 performance has improved alot including loading of tree.
I've got a couple of old v4/6 sites that happily handle 100,000+ nodes in terms of serving up content to the users. As Ismail says, the tree may be slow to load, depending on how you have structured your site. Other than that, we haven't really had any problems with it.
One other thing to note, you may need to make sure your content queries are optimised, as performing very greedy lookups (e.g. all nodes of type X from anywhere on the site) may be slow on a content set of that size. Try and make the queries as specific as possible to keep things snappy.
I think the question is whether you need to edit these nodes from the Umbraco-backend or they just get imported and have to be shown on your site.
If you import in Umbraco there will be at least one table-record per datatype per version of the node-instance. So let's say you have 12 datatypes and you save and publish a lot of times then you will add minimal 12 rows each time and eventually that can do something to the performance. Of course there are also ways to clean up older versions (so you only store the last five versions for example)
If you're not editing the news from the backend you could consider just storing these articles in a custom table and map your code to that (and do smart caching and stuff).
So I think it depends on the use.
I have made different websites with > 10,000 nodes and never had really performance issues, that couldn't be solved. But as I said it depends on a lot of factors.
If you got more information, we could think about the best strategy,
Umbraco Performance in Large scale data sites
Hello Everybody
I'm working on a news portal with a heavy updates (100 entry every day). So
Ibrahim,
We have multilingual site on v6.1.6 it has 50 language instances and roughly 9000 nodes in total so maybe about 150 nodes per instance.
The tree takes a bit of time to load. Main thing is the more properties you have the more of an impact on performance. This is for 6.1.6 v7 performance has improved alot including loading of tree.
Regards
Ismail
Hiya,
I've got a couple of old v4/6 sites that happily handle 100,000+ nodes in terms of serving up content to the users. As Ismail says, the tree may be slow to load, depending on how you have structured your site. Other than that, we haven't really had any problems with it.
One other thing to note, you may need to make sure your content queries are optimised, as performing very greedy lookups (e.g. all nodes of type X from anywhere on the site) may be slow on a content set of that size. Try and make the queries as specific as possible to keep things snappy.
I think the question is whether you need to edit these nodes from the Umbraco-backend or they just get imported and have to be shown on your site.
If you import in Umbraco there will be at least one table-record per datatype per version of the node-instance. So let's say you have 12 datatypes and you save and publish a lot of times then you will add minimal 12 rows each time and eventually that can do something to the performance. Of course there are also ways to clean up older versions (so you only store the last five versions for example)
If you're not editing the news from the backend you could consider just storing these articles in a custom table and map your code to that (and do smart caching and stuff).
So I think it depends on the use.
I have made different websites with > 10,000 nodes and never had really performance issues, that couldn't be solved. But as I said it depends on a lot of factors.
If you got more information, we could think about the best strategy,
Regards, Jeffrey
Thank you guys for the feedback.
is working on a reply...