The reason we've flagged this as a pitfall is because we see a lot of people just creating hundreds or thousands of nodes per hour, not thinking of the consequences of Umbraco's database growing really fast.
The rule of thumb is: if the content doesn't need to be managed by an editor in the Umbraco backoffice, then it should not be a content item in Umbraco.
It sounds like in both cases you should consider storing this kind of data in a custom table or possibly use Umbraco Forms for it (so you still can add workflows and approvals).
If you don't expect the amount of content to grow beyond a few hundred items then it's not so bad, but the more you drop into Umbraco, the more needs to be cached, the more memory you need, the longer it takes to rebuild cache and Examine indexes, the longer it takes for your site to restart, etc.
For simple registration of leads we use Umbraco Forms. We have a site running now with 208k entries in one form and it can still run exports and show data.
Using Umbraco content items for volatile data
Hi all,
when reading the Common pitfalls in Umbraco, I came on the Using Umbraco content items for volatile data:
Common pitfalls - Using Umbraco content items for volatile data
In the docs I see the following:
So in one website I have created I do this for reviews that visitors can add using a form.
In another website we are building we have something simular, a form to registrate a customer as a lead, so we add this into the backoffice.
Is this bad practise and do we need to create a custom table for this?
Because for the reviews, we want to add this to the front end website, the second example is for internal purposes to link to other ERP systems.
/Michaël
The reason we've flagged this as a pitfall is because we see a lot of people just creating hundreds or thousands of nodes per hour, not thinking of the consequences of Umbraco's database growing really fast.
The rule of thumb is: if the content doesn't need to be managed by an editor in the Umbraco backoffice, then it should not be a content item in Umbraco.
It sounds like in both cases you should consider storing this kind of data in a custom table or possibly use Umbraco Forms for it (so you still can add workflows and approvals).
If you don't expect the amount of content to grow beyond a few hundred items then it's not so bad, but the more you drop into Umbraco, the more needs to be cached, the more memory you need, the longer it takes to rebuild cache and Examine indexes, the longer it takes for your site to restart, etc.
For the reviews I won't expect this, but for the second project the customer was talking about 2000 possible leads.
So, maybe we indeed need to go creating a custom table for this.
Thanks for the intel!
/Michaël
For simple registration of leads we use Umbraco Forms. We have a site running now with 208k entries in one form and it can still run exports and show data.
is working on a reply...