The maproulette leaderboard is a sql table that is updated on some interval. When users send a request for their score, it is fetched from the pre-computed leaderboard in most cases.
However if the userid <:id> is not in the table, it causes the table to be generated in RAM per request. The system is not sufficiently large enough to handle even a few of those requests and the site may fail.
To avoid this, these endpoints must send back errors to the request and NEVER generate the in-memory leaderboard:
The maproulette leaderboard is a sql table that is updated on some interval. When users send a request for their score, it is fetched from the pre-computed leaderboard in most cases.
However if the userid <:id> is not in the table, it causes the table to be generated in RAM per request. The system is not sufficiently large enough to handle even a few of those requests and the site may fail.
To avoid this, these endpoints must send back errors to the request and NEVER generate the in-memory leaderboard:
/data/user/:id/leaderboard
/data/user/:id/topChallenges