On 27/05/2010 8:38 PM, Ralph Versteegen wrote:
On 28 May 2010 11:25, James Paige<[email protected]>  wrote:
On Thu, May 27, 2010 at 07:07:38PM -0400, Mike Caron wrote:
On 27/05/2010 6:38 PM, James Paige wrote:
Mike, was there any special reason why Reload.SerializeXML uses print
statements rather than writing to a file?

---
James

I wrote it as a debugging function. If it wrote to a file, then I
wouldn't be able to see it on screen in reloadtest! :)
--
Mike

I guess what I am really looking for is a reload2xml command-line tool
so I can easily debug reload files on disk..

and actually it doesn't matter that SerializeXML prints to the console,
because I could just do

  reload2xml somefile.reld>  somefile.xml

---
James

Writing to standard output is the Unix way anyway!

Speaking of xml, Mike mentioned a couple weeks ago that the Reload
code grinds to a halt when processing some translated 64MB xml
document. Since I enjoy optimisation to a rather evil degree, I'd like
to look at it sometime. What are some good testcases?

Right at this moment, I don't feel like touching any of that stuff, so go nuts.

A few tips:

- I don't think the private heap has anything to do with potential performance issues. They're the same calls being done by the runtime, just in a different memory block. - One thing I never thought about doing is compiling with the -profile switch. - I never did any formal performance tuning, being as I subscribe to the "make it work, then make it fast" camp. All that ZString crap was to alleviate my fears of memory corruption caused by having Strings in UDTs.

This is the document I mentioned: (warning: ~5 Megs compressed, 64 Megs uncompressed)

http://taleotc.com/medline08n0059.zip

I haven't looked to closely at the structure of the document, but it seems to be a fairly average, if large, dataset.

Other than that, Google isn't being very friendly. Querying "xml test documents" lists a bunch of XML Tutorials and Unit testing stuff, while "large xml test documents" seems to focus on *really* big documents (like, > 1 Gb), for which I suspect the RELOAD file format would break down :)

--
Mike
_______________________________________________
Ohrrpgce mailing list
[email protected]
http://lists.motherhamster.org/listinfo.cgi/ohrrpgce-motherhamster.org

Reply via email to