Weird rumble scores

Fragment of a discussion from Talk:BeepBoop
← Thread:Talk:BeepBoop/Weird rumble scores/reply (15)

Jump to navigation Jump to search

I think you are right. Clients should be allocated with one extra core for GC to be ran on background. Forcing full GC each round could also be added to rumble client.

And I think the extra core should be enforced by rumble clients

Anyway the optimal cpu ratio needs some experiments, but battles seems to run even faster when some cores are dedicated for GC.

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.

And I’m not sure whether rumble clients shall be restarted after many battles. If there were some memory leaks in robocode, performance will drop overtime, resulting APS drop in newer bots.

Return to Thread:Talk:BeepBoop/Weird rumble scores/reply (16).

It's not per-round so much as per-battle, but I will note that Robocode does make some System.gc calls at end of battle.

It's also the case for a very long time I've been in a habit of including System.gc() in the constructor of my bots, so that'd end up being per round.

Rednaxela (talk)‎

Retrieved from "http://robowiki.net/wiki/Thread:Talk:BeepBoop/Weird_rumble_scores/reply_(15)#Weird_rumble_scores_6802"