Alberto Massari wrote:
Hi Scott,
DOMDocument nodes keep a list of memory blocks used to allocate all the
nodes belonging to its tree; using a memory pool allows faster node
creation and deletion. These chunks are by default 64Kb big, and there
will always be at least one chunk allocated (inside the constructor
there is an allocation that force the allocation of the first memory
chunk). I don't see how this could be easily changed, so the quick fix
for your problem would be to reduce that value to a level that doesn't
waste too much memory but doesn't hurt performances too much.
Sure, but wouldn't it make sense for that to be configurable by the
application? Making people recompile Xerces doesn't really allow it to
be changed in an effective way. And the change would be pretty trivial.
I'll file a bug on it.
-- Scott
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
