tag:blogger.com,1999:blog-33823279.post7625786150095477237..comments2017-09-30T20:24:39.050-05:00Comments on Learning to Talk: Weekend FollowupJeffrey Massunghttp://www.blogger.com/profile/04030428048626948495noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-33823279.post-55354474641543503582007-03-12T15:38:00.000-05:002007-03-12T15:38:00.000-05:00It certainly sounds like the problem is the GC ina...It certainly sounds like the problem is the GC inability to cope with lots of short lived objects. There are all kinds of GCs with different performance profiles and the (possible...) problems shouldn't be over generalized.<BR/><BR/>I believe that with a decent generational GC there shouldn't be any problem, I have run some of my GCed games with age old PIIs and there never was any GC related issues.<BR/><BR/>Or maybe the Dolphins FFI adds some overhead, it's quite possible that it never was designed to be used like this. For example, some years ago I had GC problems with CMUCL and it turned out that for some reason even calling a foreign function like 'void foo(void)' repeatedly allocated ridiculous amounts of memory.<BR/><BR/>Hope you got it sorted out :)Flatlanderhttps://www.blogger.com/profile/03404534722590011501noreply@blogger.com