BIND 10 #1028: Large memory footprint for b10-xfrin
BIND 10 Development
do-not-reply at isc.org
Wed Oct 26 13:44:18 UTC 2011
#1028: Large memory footprint for b10-xfrin
-------------------------------------+-------------------------------------
Reporter: shane | Owner: jinmei
Type: | Status: reviewing
defect | Milestone:
Priority: major | Sprint-20111108
Component: xfrin | Resolution:
Keywords: | Sensitive: 0
Defect Severity: | Sub-Project: DNS
Medium | Estimated Difficulty: 9
Feature Depending on Ticket: | Total Hours: 0
Add Hours to Ticket: |
Internal?: 0 |
-------------------------------------+-------------------------------------
Changes (by jelte):
* owner: jelte => jinmei
Comment:
One comment on the code, there is a //TODO comment there, and it is now
above the wrong code (it talks about whether the get_section should really
return an iterator or not). We should either remove it or move it back to
the function itself (not opposed to just removing the suggestion entirely)
Code looks good. I did however find that when I repeatedly send retransfer
commands, it still looks like b10_ixfr keeps growing in size...
Have you just been going through code or did you use some form of memory
tracking system?
--
Ticket URL: <http://bind10.isc.org/ticket/1028#comment:11>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list