From: Kevin G. <ke...@co...> - 2009-08-15 09:03:27
|
We're currently using the java to iphone objc library and finding performance issues with the default option of having an AutoReleasePool for every class/method. We're focusing on games at the moment so we're finding that the only class we want the pool in is the main class managing the game loop and then applying the annotation NoAutoReleasePool to every other class to let auto the garbage management happen on the release at the end of the game loop. Is it advised to have so many auto release pools since they seem to have a high performance overahead. Still going great here tho :) (Patch is in progress again) Kev |