From: Andrew Haley <aph@redhat.com>
To: Herman ten Brugge <hermantenbrugge@home.nl>
Cc: Tom Tromey <tromey@redhat.com>, java@gcc.gnu.org
Subject: Re: very slow jni code callbacks
Date: Mon, 28 Sep 2009 20:13:00 -0000 [thread overview]
Message-ID: <4AC118E0.7000507@redhat.com> (raw)
In-Reply-To: <4AC112E0.5090209@home.nl>
Herman ten Brugge wrote:
> I did try some older gcc releases because I once had good
> results for callbacks.
> The 4.1.2 release shows some different results.
>
> # open jdk gcj
> # no_jni 1.48 12.12 ( 8 times slower)
> # jni 66.70 200.93 ( 3 times slower)
>
> So there must be a change some time ago that made this
> much slower.
It depends only on the number of active ClassLoaders, and how much
processing they do. The fix for this is to remove the classname
lookups at runtime.
Andrew.
prev parent reply other threads:[~2009-09-28 20:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-27 13:23 Herman ten Brugge
2009-09-28 12:03 ` Andrew Haley
2009-09-28 12:10 ` Bryce McKinlay
2009-09-28 12:13 ` Andrew Haley
2009-09-28 19:01 ` Tom Tromey
2009-09-28 19:01 ` Tom Tromey
2009-09-28 19:47 ` Herman ten Brugge
2009-09-28 20:13 ` Andrew Haley [this message]
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=4AC118E0.7000507@redhat.com \
--to=aph@redhat.com \
--cc=hermantenbrugge@home.nl \
--cc=java@gcc.gnu.org \
--cc=tromey@redhat.com \
/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).