Home/ Questions/Q 8355863
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-09T09:59:31+00:00

I am trying to write a xml parser for my game, since the size

  • 0

I am trying to write a xml parser for my game, since the size of the final build increase by 1+ mb when using the system.xml namespace. The parser class is a singleton and will be ready for access anytime in the game. Though the amount of data I am going to handle is not much, I am still worried about the performance (since it is a game, I cannot afford to sacrifice any performance).

Is there any way to effectively handle the parsing. Btw i am using c# and if a tag named <tag> is there, I am just breaking down the string into pieces searching for <tag> and </tag>. This will continue recursively until the whole string is broken down completely. And the result will be saved in a jagged list class I have created.

Are there any ways, I can improve my method or should I just go with System.XML name space.

Also another note: The xml data is from server not from a local file.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Some notes (this should be a comment, but is too long):

    1. I could not reproduce your problem. Using a console application, I added a reference to System.Xml, created an XmlDocument, used it, and compiled, and didn’t see any meaningful increase in size.
    2. System.Xml is part of the .Net base class library. Generally, you can count on it being on every machine that runs .Net (according the msdn, XmlDocument is available in XNA, for example, but not on the portable class library).
    3. If it is a part of your framework, make sure you did not set Copy Local = True on the reference. The default should be false, but if it is true, it will copy a 900 KB DLL to your target folder.
    4. No one can ever answer which is faster – The answer is extremely relative – to what types of XMLs (small? large?)? On what types of machines? What operations will your users do more with these XMLs? Only you can answer these questions, by profiling your code.
    5. Even if you discover XmlDocument is slow or too large, there are countless XML parsers for .Net – maybe one of them is good for you. (even .Net has XDocument, but it also requires System.Xml.dll, so no gain there)
    6. Generally, multiple string manipulations are slow. If the method you describe is constantly searching and splitting the sting, it sounds slow – I doubt you need to scan the string more than once to parse XML.
    • 0