Brutus5000 wrote:
As far as I have understood Arkitekt's solution is a stateless server, that queries all of the ladder games inside the ladder week timespan, processes them and cache the result for 15 minutes. After 2 days he hit the current RAM limit of our API. The limit was set very low (256mb) - but that was 2 days. Can you imagine what would happen if he queries the games of a whole year?
But fear not: The ladder divisions will return (it's already coded in the java server). But not in 2017.
And hopefully someone will put it into the website then. (We have a serious lack of web developers and I'd be glad i Arkitekt would join the team.)
that was the original plan
I actually ended up having to persist data as I needed to maintain the first reported ladder rating for the week to determine a player's division. It calls the api every 5 mins but is only fetching games for the last 3 hours so it shouldn't have been too much load? i doubt it has needed to get a page 2 at all with the smaller window its using for updates.Statistics: Posted by arkitect — 15 Dec 2017, 12:13
]]>