Introducing RBStats

[NobleHelium]

This doesn't really solve the problem but you could save more data by redesigning your tables a bit. I assume one of your rows currently looks like this:

thread_id, thread_name, metric_count, date

So you have one row per thread per day (per metric). That's a lot of rows. The other way to do it is to have one row per thread and then one column per day, but then you would have an ever-expanding number of columns which is obviously stupid design. But you can have something in between, where you have one row per thread every week or every month, and then 7 columns for each day of the week or 31 columns for each day of the month. That would reduce your row count a lot, and I don't think Heroku is going to complain about a few more columns.

[WilliamLP]

Yeah, it's that right now. Threads are normalized into a table, metrics are not. (post_count, view_count). TBH I think I'd rather pay the money rather than add complexity for a hack. I think I'm just going to chop off old months to keep rows under 9000 or something. But I'm pleasantly surprised this has consumers!

[spacetyrantxenu]

No better way to visually monitor progress toward a post domination victory! Great tool.

[thestick]

Data still isn't updating.

[WilliamLP]

This should be working now. I took the easy way out and it just stats purging old months if it sees the row count get too large. There's also a gap and a spike for today in the daily counts because the algorithm just subtracts the previous count from the count to get that delta, and it skipped a bunch of days.

If losing data for old months and games bothers anyone a lot, and you have unlimited money, send me a PM.

[thestick]

How about purging the completed games?

[Old Harry]

This thread should be stickied...

[YossarianLives]

Awesome, thanks for stickying this!

[WilliamLP]

Thanks for the sticky. Is there anything else anyone would want to see out of this?

My list is maybe to find a free Python hosting solution with a database not limited to 10k rows, add an "include inactive" checkbox in the game select, and maybe add a way to limit the date range since, if the full data set were kept Highcharts would give the browser a real workout rendering the large and long games.

(Unfortunately I really like Heroku because the entire deploy is complete with only "git push heroku master", the local test build is exactly the same as production, and the interface to get the production log is really easy. E.g. I don't have to mess around with SCP and such or know how to restart services remotely.)

[Old Harry]

It doesn't seem to cope with PB18 - too many players?

If you're adding to your to do list I'd like a button that turns all the threads off and on for each graph.