Nice work and some thoughs

Jump to navigation Jump to search

The problem isn't so much total storage space, but that I'm limited at 50k writes per day. Each bot counts as 2 writes, so effectively I have 25k updates I can do. I've figured out a caching scheme so that each melee battle comes out to 10 updates (1 per bot) instead of 45 updates (1 per pairing). I also need to update the total rumble battles count and the user upload count, so that leaves a bit of overhead, meaning I can have ~2000 melee battles per day uploaded.

I'l see what ratings systems are feasible..

Skilgannon‎17:25, 28 May 2012

You do not have permission to edit this page, for the following reasons:

  • The action you have requested is limited to users in the group: Users.
  • You must confirm your email address before editing pages. Please set and validate your email address through your user preferences.

You can view and copy the source of this page.

Return to Thread:Talk:LiteRumble/Nice work and some thoughs/reply (4).

I've actually figured out a sort of temporary caching between requests where I wait for bots to accumulate a certain number of pairings before pushing them to disk. I don't think it's necessary to re-work the rumble upload protocol yet. One thing I would like the rumble to tell me is how many bots are in a melee battle though. Right now I just have it hardcoded at 10. It would help with my caching if I knew how many they were uploading per battle.

Skilgannon‎20:36, 28 May 2012

Flush them to the database on a period basis (constant number of commits regardless of number of uploads) instead of being per number of uploads?

MN‎20:52, 28 May 2012
 
 
 
Retrieved from "http://robowiki.net/wiki/Thread:Talk:LiteRumble/Nice_work_and_some_thoughs/reply_(3)#Nice_work_and_some_thoughs_850"