public inbox for java@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andrew Haley <aph@redhat.com>
To: ffileppo <ffileppo@libero.it>
Cc: java <java@gcc.gnu.org>, classpath <classpath@gnu.org>
Subject: Re: [GCJ] Performance of GUI applications on embedded systems
Date: Fri, 07 Nov 2008 18:56:00 -0000	[thread overview]
Message-ID: <49148F35.8030209@redhat.com> (raw)
In-Reply-To: <K9YMPL$EE8A6F8D456C503AD6F47FAE27B666E7@libero.it>

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.
>>
> 
> You're right.
> However I'm experiencing slowness when testing some other GUI sample application (e.g. the test case attached at the end).
> 
> In this particular test case, the application takes a lot of time to startup (compared to the same device, running WinCE and CrEme JVM) and during start up the CPU usage is always at 100%.
> 
> After startup, I'v also noticed that highlighting and/or clicking a certain number of times on buttons cause the application to hang and after that the CPU usage is always 100%.

I've identified some serious GTK locking problems with this version of gcj.

I'm investigating.

Andrew.

  parent reply	other threads:[~2008-11-07 18:56 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-07 11:04 ffileppo
2008-11-07 11:18 ` Andrew Haley
2008-11-07 18:56 ` Andrew Haley [this message]
2008-11-08 11:40   ` Andrew Haley
2008-11-08 12:47     ` Andrew Haley
2008-11-09  0:25       ` Andrew John Hughes
2008-11-09 10:11         ` Mark Wielaard
2008-11-09 13:55         ` Andrew Haley
  -- strict thread matches above, loose matches on Subject: below --
2008-11-10  8:55 ffileppo
2008-11-10 10:20 ` Andrew Haley
2008-11-06 13:40 ffileppo
2008-11-06 16:40 ` Andrew Haley
2008-11-06 17:02   ` Christian Thalinger
2008-11-05 13:53 ffileppo
2008-11-05 14:07 ` Andrew Haley
2008-11-05 14:26   ` Andrew Haley
2008-11-05  8:24 ffileppo
2008-11-05  9:44 ` Andrew Haley
2008-11-05  9:45 ` Mark Wielaard
2008-11-05  9:50   ` Andrew Haley
2008-11-03 12:51 ffileppo
2008-11-03 14:53 ` Andrew Haley
2008-11-03 15:04   ` Andrew Haley
2008-11-03  7:38 ffileppo
2008-11-03 10:37 ` Andrew Haley
2008-11-03 12:02   ` Andrew Haley
2008-11-03 12:54     ` Andrew Haley
2008-11-03 13:02       ` Roman Kennke
2008-11-03 13:14         ` Andrew Haley
2008-11-03 15:46     ` Andrew Haley

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=49148F35.8030209@redhat.com \
    --to=aph@redhat.com \
    --cc=classpath@gnu.org \
    --cc=ffileppo@libero.it \
    --cc=java@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).