You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@xerces.apache.org by "Scott Cantor (JIRA)" <xe...@xml.apache.org> on 2008/09/15 16:17:46 UTC
[jira] Commented: (XERCESC-1821) Configurable
kInitialHeapAllocSize in xerces
[ https://issues.apache.org/jira/browse/XERCESC-1821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12631032#action_12631032 ]
Scott Cantor commented on XERCESC-1821:
---------------------------------------
I will test it by tomorrow, but that sounds fine for my purposes. Thanks.
> 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
> Assignee: Boris Kolpackov
> Priority: Minor
> Fix For: 3.0.0
>
> Attachments: DOMDocumentImpl.cpp, DOMDocumentImpl.hpp
>
>
> 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: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org