|
I reproduced this as follows. First, start up a mongod instance with --smallfiles. Then create 100 databases:
for (var i = 0; i < 100; i++) { db.getSisterDB("test" + i).foo.insert({_id: 1}); }
|
Shut down and start a 2.6.6 mongod with the same dbpath. The mem section of server status shows the following:
> db.version()
|
2.6.6
|
> db.serverStatus().mem
|
{
|
"bits" : 64,
|
"resident" : 1637,
|
"virtual" : 6654,
|
"supported" : true,
|
"mapped" : 3232,
|
"mappedWithJournal" : 6464
|
}
|
Starting up a build of latest in master, virtual and resident memory are much higher, though mapped is the same:
> db.version()
|
2.8.0-rc3-pre-
|
> db.serverStatus().mem
|
{
|
"bits" : 64,
|
"resident" : 3641,
|
"virtual" : 8667,
|
"supported" : true,
|
"mapped" : 3232,
|
"mappedWithJournal" : 6464
|
}
|
After changing to a singleton RecordAccessTracker, the mem stats go back to what they were for 2.6.6.
> db.version()
|
2.8.0-rc3-pre-
|
> db.serverStatus().mem
|
{
|
"bits" : 64,
|
"resident" : 1640,
|
"virtual" : 6665,
|
"supported" : true,
|
"mapped" : 3232,
|
"mappedWithJournal" : 6464
|
}
|
|