Difference between revisions of "Talk:WeeksOnEnd"
Jump to navigation
Jump to search
(→OutOfMemory errors: no iteration) |
Darkcanuck (talk | contribs) (→OutOfMemory errors: priority battles same in either case) |
||
| Line 8: | Line 8: | ||
:: I don't use ITERATE=YES because my cpu overheats when I do, and what I think happens to priority battles is that it fights about two battles against each bot instead of one, but that is just hunch, there has been no investagation to support it. --[[User:Zyx|zyx]] 13:52, 9 September 2009 (UTC) | :: I don't use ITERATE=YES because my cpu overheats when I do, and what I think happens to priority battles is that it fights about two battles against each bot instead of one, but that is just hunch, there has been no investagation to support it. --[[User:Zyx|zyx]] 13:52, 9 September 2009 (UTC) | ||
| + | |||
| + | :: There shouldn't be any difference with priority battles whether you're iterating within RoboRumble or using a shell script. Each time your client uploads results, the server sends back priority battles which get saved in a file for the next iteration. What battles you get is determined by what you uploaded. My client doesn't use the iterate flag and is constantly filling out pairings... --[[User:Darkcanuck|Darkcanuck]] 15:22, 9 September 2009 (UTC) | ||
Revision as of 16:22, 9 September 2009
OutOfMemory errors
Anyone else had issues with any of Simonton's bots lately? Last night, 3 of my 4 clients were hung with "java.lang.OutOfMemoryError: Java heap space" from WeeksOnEnd 1.10.4 battles, and I've had it happen with another of his bots recently, too (LifelongObsession maybe?). And, sadly, my 4th client hung with the same error from RougeDC willow. =( --Voidious 13:03, 9 September 2009 (UTC)
I used to get those, but they stopped when I changed from iterating within roborumble (ie. ITERATE=YES in roborumble.txt) to iterating in a shell script instead (ie. while sleep 1; do ./roborumble.sh; done). I suspect Robocode still isn't releasing all the memory from bots. --Skilgannon 13:10, 9 September 2009 (UTC)
- Hmm, I'll have to switch if that solves the problem... The issue with that is that it doesn't seem to recognize priority battles as well on the first iteration, at least that's what I've seen. The first iteration, it just seems to look at the BATTLESPERBOT, while on successive iterations, it tries to fill all pairings. I'll tinker with it later though. Thanks! --Voidious 13:12, 9 September 2009 (UTC)
- I don't use ITERATE=YES because my cpu overheats when I do, and what I think happens to priority battles is that it fights about two battles against each bot instead of one, but that is just hunch, there has been no investagation to support it. --zyx 13:52, 9 September 2009 (UTC)
- There shouldn't be any difference with priority battles whether you're iterating within RoboRumble or using a shell script. Each time your client uploads results, the server sends back priority battles which get saved in a file for the next iteration. What battles you get is determined by what you uploaded. My client doesn't use the iterate flag and is constantly filling out pairings... --Darkcanuck 15:22, 9 September 2009 (UTC)
