Hi,
We are developing some SharePoint 2010 solutions which involves sometimes to process (insert/update) items huge lists. Once I found the method SPWeb.ProcessBatchData I thought we won't have any performance problems but after I tested a little bit I was completely disappointed (unfortunately SharePoint itself is kind of disappointing environment for developers). To insert 5.000 items (one normal text field) in a list took around 40 seconds. I checked with SQL Profiler and I saw there are a lot of round trips to SQL Server from SharePoint (probably 5000+). I was expecting more from Microsoft. Why they couldn't implement a Stored Procedure at SQL Server level which receives an XML and returns an XML with results? I know that inserting a simple list item requires a lot of operations against database but still the SQL round trips are downgrading the performance way too much...
Is there any chance in the future to improve or to offer some more performant methods to developers? I mean for 5000 items I think 40 seconds is way way too much.