What do you think about a GigaMeleeRumble?

Jump to navigation Jump to search

Literumble is up and running, accepting contributions. There is a static copy of the old data at staticrumble.appspot.com. I'll keep an eye on it from my side, and please let me know if you see any issues with your clients. In a few days, when we're sure everything is working, I'll delete the data and we can start from fresh.

Skilgannon (talk)10:16, 4 May 2014

All my clients show in rumble and meleerumble

OK. Queue full,Wisdom vs GridFu discarded.

naturally, with different bots name.

There is something fishy, since than I see the same bot pair added to queue over and over with messages like this

OK. Wisdom vs GridFu added to queue in 41ms

Beaming (talk)15:50, 4 May 2014

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:RoboRumble/Rule Suggestions/What do you think about a GigaMeleeRumble?/reply (36).

I think I found the problem. Have to delete content of files and temp directories. Files dir contained the results1v1.txt file with 12MB size which sounds excessive.

Beaming (talk)06:19, 6 May 2014

It seems to be stuck at 'queue full' most of the time.

Regarding the same bot pair added multiple times, perhaps you're referring to how it has to upload once for each rumble that's fitting for the pair of bots? (i.e. the different size categories)

Rednaxela (talk)17:11, 4 May 2014

The reason the queue is full so much is that uploads are happening at a rate of ~35/s, but I can only process ~5/s. I'll work more on optimising load and store times, but there is only so much I can do with that...

Skilgannon (talk)18:37, 4 May 2014

We could upgrade the rumble protocol to implement bulk uploads, allowing bulk commits in the server.

MN (talk)01:49, 6 May 2014

Uh... somebody's client is misconfigured, and uploading a bunch of stuff to the Minirumble which doesn't belong.

For example, "simonton.beta.LifelongObsession 0.5.1" is a Megabot.

Can folks who are currently contributing check that their client isn't doing this please?

Rednaxela (talk)01:46, 7 May 2014

Where to look for it?

Beaming (talk)02:39, 7 May 2014

Beaming, looking at logs it seems to be coming from one of your clients. I see in the Robocode release notes that fixed a bug with the codesize generation. Which Robocode version are you running?

Skilgannon (talk)08:57, 7 May 2014

Does it come from IP starting from 70 or 128?

The one at 70 somehow does not generate codesize1v1.txt file, though they all run robocode-

Any advise would be welcome.

Beaming (talk)13:57, 7 May 2014