DOM is the wrong choice for unmarshalling XML data from a protocol. The DOM is slow and bloated. You need that if you are manipulating an XML document, but not if you are stripmining the data from it then throwing the document away.
Try a StAX parser: http://en.wikipedia.org/wiki/StAX That should be simpler and much, much faster. wunder On Nov 12, 2009, at 10:01 AM, Mauricio Scheffer wrote: > I use DOM. Honestly, I haven't run any perf tests, it all just runs well > enough for me. Then again, my documents and resultsets are typically small > (~1KB docs and ~50 docs per resultset). How big are your documents? > > > On Thu, Nov 12, 2009 at 2:40 PM, wojtekpia <wojte...@hotmail.com> wrote: > >> >> I was thinking of going this route too because I've found that parsing XML >> result sets using XmlDocument + XPath can be very slow (up to a few >> seconds) >> when requesting ~100 documents. Are you getting good performance parsing >> large result sets? Are you using SAX instead of DOM? >> >> Thanks, >> Wojtek >> >> >> mausch wrote: >>> >>> It's one of my pending issues for SolrNet ( >>> http://code.google.com/p/solrnet/issues/detail?id=71 ) >>> I've looked at the code, it doesn't seem terribly complex to port to C#. >>> It >>> would be kind of cumbersome to test it though. >>> I just didn't implement it yet because I'm getting good enough >> performance >>> with XML (and other people as well: >>> http://groups.google.com/group/solrnet/msg/4de8224a33279906 ) >>> >>> Cheers, >>> Mauricio >>> >> >> -- >> View this message in context: >> http://old.nabble.com/javabin-in-.NET--tp26321914p26323001.html >> Sent from the Solr - User mailing list archive at Nabble.com. >> >>
