We are developing a site which currently contains approximately 10K content nodes. Each content node has about 30 properties (on average).
Currently we are experiencing problems with the cmsContentXml table being out of sync. This leads to all kind of problems and therefore we have tried to get the cmsContentXml into sync again.
Primarily we have tried using the "/umbraco/dialogs/republish.aspx?xml=true" functionality and that certainly seems to be what we are looking for... however...
Due to how the RePublish functionality is implemented it seems as if it will never be able to finish (given our content).
From what we understand (by looking at the Umbraco source) - the idea is to populate a List<IContent> which will then be iterated. Each IContent will be converted to a xml string which will eventually be inserted into cmsContentXml.
In our case - populating the List<IContent> will require approximately 300K(!) SQL queries (10K Content * 30 Properties) and since the application doesn't seem to get a chance to release memory it will eventually have to recycle the AppPool before anything has actually been inserted into cmsContentXml.
We have thought about creating a dashboard with our own functionality which would rebuild the cmsContentXml table in a more efficient manner.
Rebuilding cmsContentXml
We are developing a site which currently contains approximately 10K content nodes.
Each content node has about 30 properties (on average).
Currently we are experiencing problems with the cmsContentXml table being out of sync. This leads to all kind of problems and therefore we have tried to get the cmsContentXml into sync again.
Primarily we have tried using the "/umbraco/dialogs/republish.aspx?xml=true" functionality and that certainly seems to be what we are looking for... however...
Due to how the RePublish functionality is implemented it seems as if it will never be able to finish (given our content).
From what we understand (by looking at the Umbraco source) - the idea is to populate a List<IContent> which will then be iterated. Each IContent will be converted to a xml string which will eventually be inserted into cmsContentXml.
In our case - populating the List<IContent> will require approximately 300K(!) SQL queries (10K Content * 30 Properties) and since the application doesn't seem to get a chance to release memory it will eventually have to recycle the AppPool before anything has actually been inserted into cmsContentXml.
We have thought about creating a dashboard with our own functionality which would rebuild the cmsContentXml table in a more efficient manner.
Is there any better way around this problem?
is working on a reply...