Performance: XmlTextReader vs LINQ to XML

Question

I'm about to read some XML (who isn't :-)). This time however it's a lot of data: about 30,000 records with 5 properties, all in one file.

Till now I've always read that the XmlTextReader is the fastest way to read XML data, but now there also is the (nice syntax of) LINQ to XML.

Does anybody know any performance issues, or that there aren't any, with LINQ to XML?

Michel

I hate to disappoint you, but 30000 records is not "a lot of data" — Mitch Wheat, Jun 07 '10 at 09:48
Do not use XmlTextReader anymore. http://stackoverflow.com/questions/8096564/xmltextreader-vs-xdocument — nawfal, Aug 20 '15 at 06:29

score 2 · Accepted Answer · answered Jun 07 '10 at 10:18

The API supplied by LINQ to XML is much nicer than the low level API of the XmlTextReader. This will result in code that is much more maintainable. As Mitch Wheat already said, 30,000 records is not that much. IMO you should just use LINQ to XML and only when you notice LINQ to XML is too slow, fallback to using the XmlTextReader directly.

Performance: XmlTextReader vs LINQ to XML

1 Answers1