[
https://issues.apache.org/jira/browse/XERCESC-1821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alberto Massari reopened XERCESC-1821:
--------------------------------------
I am not worried about the constructor, but about the allocate() function; but
it turns out that the penalty is only 3% of the single instruction time, and
this doesn't change the overall impact of the whole function (that is around 6%
of the parsing time). As it looks it's acceptable to the community to have such
a feature, I am reopening the bug; David, can you take care of it?
Alberto
> Configurable kInitialHeapAllocSize in xerces
> ---------------------------------------------
>
> Key: XERCESC-1821
> URL: https://issues.apache.org/jira/browse/XERCESC-1821
> Project: Xerces-C++
> Issue Type: Improvement
> Components: DOM
> Environment: All OS
> Reporter: george
> Priority: Minor
> Fix For: 3.0.0
>
>
> The default DOM initial heap size is 16k in the latest release (earlier
> release was 64k). this number could be still too big or too small for some
> system.
> The idea is to make the following parameters configurable in the constructor
> via a singleton read function.
> static XMLSize_t kInitialHeapAllocSize = 0x4000;
> static XMLSize_t kMaxHeapAllocSize = 0x20000;
> static XMLSize_t kMaxSubAllocationSize = 0x1000; // Any request for more
> bytes
> Now the question is if you think this is a valuable suggestion? I have a
> working code and would like to share if you think it worth the effort.
> Cheers
> George
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
