Comments on: READ BEFORE USING IT – Open XML SDK performance analysis http://blog.goyello.com/2009/08/25/read-before-using-it-open-xml-sdk-performance-analysis/ Sharing our daily IT experience Fri, 30 Jul 2010 20:03:22 +0200 http://wordpress.org/?v=2.8.6 hourly 1 By: louis vuitton for sale http://blog.goyello.com/2009/08/25/read-before-using-it-open-xml-sdk-performance-analysis/comment-page-1/#comment-791 louis vuitton for sale Fri, 04 Jun 2010 12:38:01 +0000 http://blog.goyello.com/?p=759#comment-791 I like writing, hurriedly, not that you are not<br><a href="http://www.oantcogs.com" rel="nofollow">http://www.oantcogs.com</a> I like writing, hurriedly, not that you are not
http://www.oantcogs.com

]]> By: Maciej Greń http://blog.goyello.com/2009/08/25/read-before-using-it-open-xml-sdk-performance-analysis/comment-page-1/#comment-685 Maciej Greń Tue, 01 Jun 2010 20:09:56 +0000 http://blog.goyello.com/?p=759#comment-685 Thank you for your comment and good word. Thank you for your comment and good word.

]]> By: public records http://blog.goyello.com/2009/08/25/read-before-using-it-open-xml-sdk-performance-analysis/comment-page-1/#comment-630 public records Wed, 28 Apr 2010 16:43:54 +0000 http://blog.goyello.com/?p=759#comment-630 hi, i see this site and i think there are more information which is help people! hi, i see this site and i think there are more information which is help people!

]]> By: Patrick http://blog.goyello.com/2009/08/25/read-before-using-it-open-xml-sdk-performance-analysis/comment-page-1/#comment-548 Patrick Tue, 09 Feb 2010 06:13:03 +0000 http://blog.goyello.com/?p=759#comment-548 Did they fix the buffering problem in OpeXml Document 2.0 (CTP December) version? have you ran these test using the newest version? Did they fix the buffering problem in OpeXml Document 2.0 (CTP December) version? have you ran these test using the newest version?

]]> By: anon http://blog.goyello.com/2009/08/25/read-before-using-it-open-xml-sdk-performance-analysis/comment-page-1/#comment-449 anon Sat, 28 Nov 2009 02:45:41 +0000 http://blog.goyello.com/?p=759#comment-449 You may want to look at vtd-xml as the state of the art in XML processing, consuming far less memory than DOM<br><br><a href="http://vtd-xml.sf.net" rel="nofollow">http://vtd-xml.sf.net</a> You may want to look at vtd-xml as the state of the art in XML processing, consuming far less memory than DOM

http://vtd-xml.sf.net

]]> By: lindabrownell http://blog.goyello.com/2009/08/25/read-before-using-it-open-xml-sdk-performance-analysis/comment-page-1/#comment-311 lindabrownell Thu, 24 Sep 2009 10:12:45 +0000 http://blog.goyello.com/?p=759#comment-311 I am not sure if the performance chart at the top is meant for speed or not and what the axis mean. But if it does mean for the performance, here is probably why: SDK stores all content of the part into the DOM tree and when Save() is called, it serializes the whole tree back into the stream and writes it out. In another word, SDK does not have a support to manipulate documents in a stream model yet. With this design, the idea of buffer records won’t help much in terms of the SDK's consumption of memory. ‘BufferSize’ could help a bit with performance as it reduces the number of calls to Save(). If user calls Save() one time after he has inserted all the records into the sheet, it is probably the fastest way – if memory is not an issue. I am not sure if the performance chart at the top is meant for speed or not and what the axis mean. But if it does mean for the performance, here is probably why: SDK stores all content of the part into the DOM tree and when Save() is called, it serializes the whole tree back into the stream and writes it out. In another word, SDK does not have a support to manipulate documents in a stream model yet. With this design, the idea of buffer records won’t help much in terms of the SDK's consumption of memory. ‘BufferSize’ could help a bit with performance as it reduces the number of calls to Save(). If user calls Save() one time after he has inserted all the records into the sheet, it is probably the fastest way – if memory is not an issue.

]]>