ffileppo wrote: >> Here's one improvement. If you can get rid of the places in the GTK peers >> where class and method lookups are performed at runtime you'll probably >> have a fix. This shouldn't be a massive amount of work, just rather >> boring. >> >> In gcj, >> >> * Compiled java code is quite fast. >> * Class lookup by name is slow. >> * Calling JNI code from compiled java code is quite fast. >> * Calling compiled java code from JNI code is slow. >> * Exceptions are slow.
> I'm testing your patch on my embedded system and now I can see that GUI > performance are very much better (particularly during application startup). > > Thank you so much! > > However running my test case (please see my first post) I see that CPU usage > is always at 100% (after the application is running), > so the responsiveness is still not very good. What do you expect? You're setting up a Timer with a delay of 0 milliseconds between events, and it's running continuously. Andrew.
