Have versions pages load only required data about codecombat HOT 6 CLOSED

Handler.coffee is located in /server/commons/Handler.coffee.

from codecombat.

I jumped this issue but found that loading versions was already quite efficient. An example response is the following:

[ { slug: 'tiny2',
    name: 'Tiny2',
    created: Mon Mar 10 2014 08:53:37 GMT+0100 (CET),
    version: { isLatestMinor: true, isLatestMajor: true, minor: 0, major: 0 },
    _id: 531d6f81baf1b1290f2f9534 } ]

The only thing possibly superfluous is slug but I'm guessing that's not too much of a bottleneck.

Since all and only essential properties are returned, with no documents, this issue can be closed.

from codecombat.

Yeah, I added a projection to it recently. I do see the system crash still when trying to load the versions for Brawlwood, complaining that the in-memory sort on the server runs out of memory and dies. So something isn't right about how it's trying to sort. @schmatz @sderickson how can we make this query not explode?

from codecombat.

I checked it out, it's not mongoose specific. Even if you tell Mongo to project, it seems like internally it's still loading the full data and take up all the Mongo resources. I tested by running this command on the mongo client:

db.levels.find({original:ObjectId('52d97ecd32362bc86e004e87')}, {name:1}).sort({created:-1})

You get the same error:

error: {
"$err" : "Runner error: Overflow sort stage buffered data usage of 33637240 bytes exceeds internal limit of 33554432 bytes",
"code" : 17144
}

from codecombat.

Use the aggregation framework. The following query works as expected:

db.levels.aggregate({
    $match: {
        "original": ObjectId('52d97ecd32362bc86e004e87')
    }
}, {
    $project: {
        "name": 1,
        "created": 1,
        "_id": 0
    }
}, {
    $sort: {
        "created": -1
    }
})

from codecombat.

Why yes, yes it did.

from codecombat.