I don't know of anyone who has pushed VistaDB that far with umbraco. Personally, I would use SQL Server (either the free Express version or the full version). SQL Server will definitely handle that amount of data well.
i had a quite small site running on VistaDB and ended up migrating it to SQL Server. The performance of the frontend was very good but the backend really sucked. Had to wait up to 45sec for publishing a node.
I don't know if anyone else has similar experience. But my advise is to use SQL Server even if you have this many nodes.
I would use Sqlserver. And even then I think the max is around 50.000 - 60.000 nodes.
You should consider if all data really should be stored in Umbraco. Usually I add a node to Umbraco containing some summary data and key information. This will ensure speedy access to the primary information without any db hits. Then I would store all related data directly in SQL tables.
I want to know the performance of Umbraco(vistadb) with 100,000+ contents nodes
I want to know the performance of Umbraco used vistadb with 100,000+ contents nodes
I want to use Umbraco to create a site use vistadb, but I really worry about the performance when nodes up to 100,000+.
who can give me answer? thanks.
I don't know of anyone who has pushed VistaDB that far with umbraco. Personally, I would use SQL Server (either the free Express version or the full version). SQL Server will definitely handle that amount of data well.
cheers,
doug.
Hi sun,
i had a quite small site running on VistaDB and ended up migrating it to SQL Server.
The performance of the frontend was very good but the backend really sucked. Had to wait up to 45sec for publishing a node.
I don't know if anyone else has similar experience. But my advise is to use SQL Server even if you have this many nodes.
/horst
Hi Sun,
I would use Sqlserver. And even then I think the max is around 50.000 - 60.000 nodes.
You should consider if all data really should be stored in Umbraco. Usually I add a node to Umbraco containing some summary data and key information. This will ensure speedy access to the primary information without any db hits. Then I would store all related data directly in SQL tables.
Hth
Jesper
is working on a reply...