Hi Scott, Scott Cantor <[EMAIL PROTECTED]> writes:
> I can certainly do that. Are there specific tests that ought to be > run apart from any of mine? You will need to build samples and tests and then run sanityTest.pl located in scripts/ on the data found in samples/data. I will also run our internal tests to make sure there is no performance degradation. > I was just reviewing it now (I hadn't actually looked at it before because I > knew 3.0 was a ways off) and I came to the same conclusion. I was assuming > he had added a new API to control the size constants globally, rather than > as part of the DOMMemoryManager class. Oh, it is actually more complicated than I thought. I don't think it will be wise to back-port all this DOMMemoryManager-related changes. How about a simplified version, that boils down to the following: 1. Split kHeadAllocSize into kInitialHeapAllocSize and kMaxHeapAllocSize with values from 3.0 branch. 2. Implement exponential growth until kMaxHeapAllocSize as in 3.0 (for that you will need to add the fHeapAllocSize variable to the DOMDocumentImpl class). While there won't be a way to tune fHeapAllocSize, the initial small value and the subsequent growth should satisfy most applications. What do you think? Thanks, Boris -- Boris Kolpackov Code Synthesis Tools CC http://www.codesynthesis.com Open-Source, Cross-Platform C++ XML Data Binding --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
