Umbraco content items for volatile data
# help-with-umbraco
r
Hey everyone! I came across the Umbraco documentation on common pitfalls, specifically the section about using a separate database table for large imports instead of Umbraco content nodes (https://docs.umbraco.com/umbraco-cms/reference/common-pitfalls#using-umbraco-content-items-for-volatile-data). I was wondering—how much data is considered 'too much' for Umbraco content nodes? Are there any benchmarks or best practices regarding performance limits before needing to switch to a custom table? Thanks in advance!
s
There's no magic number. What I usually tell people to consider is: which one of those imported nodes are you ACTUALLY ever going to edit again. If you're not going to edit them (or only in exceptional/emergency situations) then they shouldn't be nodes in Umbraco. As a bonus tip: you can use Umbraco UI builder for free for 1 collection (1 db table) in case you want to easily be able to edit imported content: https://umbraco.com/products/add-ons/ui-builder/
3 Views