Hi

I use umbraco without the cms... I mean all users uses an external website which saves content to umbraco via contentservice. Umbraco is setup to use the xml caching. When many users create content in the same time, service stops on the function which updates the xml. The server has no cpu peaks in this time... the cpu is stll on 0 % load. But in the remote debugger i can see that all threads waiting on update the xml.

I have solved this problem by disable the xml cache. To keep the speed for retrieving data i cache the content in my own cache after getting content via contentservice.

But i have an other problem. In some of my save processes i have many contentnodes. One save process can have up to 50 nodes. And saveandpublish is very slow in this part. In a test when I create 50 nodes and use only contentservice.save() process needs only 5 seconds... but with contentservice.saveandpublish() i need 80 seconds. 

In 

sourcecode i see, umbraco creates on both methods xml, save it to database for preview and "normal usage?" and push it to the publishstrategy i have not checked why but in my opinion to create lucene index of it... but when i disable the xml caching why umbraco needs create xml nodes and save it to database...? Can do some thing to prevent this?... implement my own publish strategy or do any other part to improve saveandpublish?