> It's not so trivial; making it a value that every DOMDocument can > tune means setting it in the constructor, and the interface for > creating a document doesn't have a place for it.
That wasn't what I meant. You could set it globally for all documents at start up time. Just move the constant out of that file so it can be set during init. My goal isn't perfection, it's improvement. For applications that create and hold small documents, 64k is insane. It's simply not viable. For that matter, some of the other constants involving table size are also probably too big. > Changing the global > value to be, for example, 16Kb, would cause performance problems. Chewing up memory also causes performance problems, much worse ones. ;-) I don't think any value is right or wrong. Only the application can determine what works best. > Maybe we could change the algorithm to dynamically raise the size, > e.g. start from 8Kb and reach 128Kb That would be cool too. 8k is actually about where I'm at for the time being until I see whether it has performance issues under load. -- Scott --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
