Comparing GoTo Surfing with True Surfing?

Jump to navigation Jump to search

It might be causing you to skip turns. Goto surfing does a lot more calculations in a single tick.

Otherwise I would say it is a bug, maybe with the starting conditions of your second wave surfing. Most difficult to get right for me was aligning the time I switch to surfing second wave with when I actually stop surfing the first wave in my real movement.

Skilgannon (talk)‎14:06, 1 September 2017

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:Wave Surfing/GoTo Surfing/Comparing GoTo Surfing and True Surfing?/reply (12).

My thought are, why take the risk? Making an allocation pool or hoisting the allocation outside of the loop for frequently created/deleted objects is fairly easy. Also less pressure on the GC will make a GC run during your tick less likely, so you are less likely to skip turns. Stack analysis is good, but I'm not sure how it deals with nested objects. I suspect there is still a heap allocation internally, which can be hoisted out of most loops quite easily.

Skilgannon (talk)‎22:34, 2 September 2017
 
 
Retrieved from "http://robowiki.net/wiki/Thread:Talk:Wave_Surfing/GoTo_Surfing/Comparing_GoTo_Surfing_and_True_Surfing%3F/reply_(2)#Comparing_GoTo_Surfing_with_True_Surfing.3F_5520"