one step forward, two back
The bug in dirty cache is fixed. I set the max entries down to 64 to add further stress on the system and the scripts ran longer but still I am getting a memory leak.
At the time of the memory leak, the number of blocks in use is 20,576, and 47 internal nodes. but the number of available blocks is 405. No problem here, but my concern is that in production the number of available blocks would be very much higher--and the table of available blocks is kept in a single block. Transaction count is 154 (I was not running purge history).
Here's the script I was running, where each run is processed as a single transaction:
//exercise removeWellknownName
createWellknown a1
go /a1
removeWellknownName
//removing a link
createWellknown a1
createWellknown b1
go /a1
cu
addOrderedSection l
go l
addLink b /b1
go /b1
go /a1/CU/l
remove b
go /b1
removeWellknownName
go /a1
removeWellknownName
//adopting a child
createWellknown a1
createWellknown b1
go /a1
adoptChild b /b1
go b
removeWellknownName
go /a1
removeWellknownName
//fork a child
createWellknown a1
createWellknown b1
go /a1
adoptFork b /b1
removeWellknownName
go /b1
removeWellknownName
//set well known name
createWellknown a1
go /a1
createChild b
go b
setWellknownName b1
go /a1
removeWellknownName
go /b1
removeWellknownName
//well known fork
createWellknown a1
go /a1
createChild b
go b
wellknownFork b1
go /a1
removeWellknownName
go /b1
removeWellknownName
//reorder parents
createWellknown a1
createWellknown b1
go /a1
createChild ac
go /b1
adoptChild bc /a1/ac
go bc
moveParentFirst /b1
go /b1
removeWellknownName
go /a1/ac
go /a1
removeWellknownName
//change child name
createWellknown a1
go /a1
createChild b
changeChildName b c
go c
go /a1
removeWellknownName
//change key
createWellknown a1
go /a1
lu
addOrderedSection x
addOrderedSection y
changeKey x z
go /a1
removeWellknownName
//change Classifier Section name
createWellknown a1
createWellknown b1
go /a1
cu
addOrderedSection l
go l
addLink b /b1
cu
changeKey l links
go /b1
removeWellknownName
go /a1
removeWellknownName
wellknown
0 Comments:
Post a Comment
<< Home