BIND 10 #2831: define and implement MemorySegmentMapped

[BIND 10 Development]

#2831: define and implement MemorySegmentMapped
-------------------------------------+-------------------------------------
            Reporter:  jinmei        |                        Owner:
                Type:  task          |                       Status:  new
            Priority:  medium        |                    Milestone:  Next-
           Component:  Unclassified  |  Sprint-Proposed
            Keywords:                |                   Resolution:
           Sensitive:  0             |                 CVSS Scoring:
         Sub-Project:  DNS           |              Defect Severity:  N/A
Estimated Difficulty:  0             |  Feature Depending on Ticket:
         Total Hours:  0             |  shared memory data source
                                     |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------

Comment (by jinmei):

 Replying to [comment:1 vorner]:
 > Usually, these things are done with doubling the size. Then you have at
 most half of the size wasted and the amortized amount of work done per
 adding one byte to it is constant.

 Yeah, but I was not sure if that's what we want in this case; for a
 large zone it can be several GBs, which will eventually be mapped to
 real memory.  I guess we don't like to keep 8GB of memory while we
 actually need 4.1GB (and we'll need to have the entire 8GB at least
 initially to avoid run time page fault and significant performance
 penalty, especially in the case of cold start).  So, in my experiment
 I doubled the size until it reaches 64MB (arbitrary choice) and
 increment it by 64MB after that.  But I'm not sure if that was a
 reasonable choice.

-- 
Ticket URL: <http://bind10.isc.org/ticket/2831#comment:4>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development