From: Andreas Rottmann <a.rottmann@gmx.at>
To: guile-gtk@sources.redhat.com
Subject: Re: Speedups for GTK2 bindings?
Date: Wed, 27 Aug 2003 04:26:00 -0000 [thread overview]
Message-ID: <878ypg8fvb.fsf@alice.rotty.yi.org> (raw)
In-Reply-To: <87ekzgnrmd.fsf@alice.rotty.yi.org> (Andreas Rottmann's message of "Wed, 20 Aug 2003 19:52:42 +0200")
Andreas Rottmann <a.rottmann@gmx.at> writes:
> Andy Wingo <wingo@pobox.com> writes:
>
>> On Tue, 19 Aug 2003, Andreas Rottmann wrote:
>>
>>> I'll probably try what speedups result of re-implementing the
>>> re-export-bindings and functions->methods-public helpers in C.
>>
>> Great! A lot of that code is (as you know) slow slow slow slow slow, and
>> since I don't fire up the gtk side of things too often, I don't really
>> see it very much.
>>
> It seems that the speed gains from doing the generics stuff from C
> (I've made up a version that is basically the scheme code translated
> to the Guile C API) are minimal at best. I think that the add-method
> invocation is the slow call. I've yet to profile the code to see what
> causes it to run so slow.
>
I've now checked in most of my non-GError related changes to
guile-gobject. This includes creating the generic functions immediatly
(as suggested by Andy Wingo), not in a seperate pass, which is cleaner
IMO and also reduces the binding load time by about 10% on my machine
(10 seconds -> 9 seconds -- YMMV, I'd like to get this number
verified...)
Regards, Andy
--
Andreas Rottmann | Rotty@ICQ | 118634484@ICQ | a.rottmann@gmx.at
http://www.8ung.at/rotty | GnuPG Key: http://www.8ung.at/rotty/gpg.asc
Fingerprint | DFB4 4EB4 78A4 5EEE 6219 F228 F92F CFC5 01FD 5B62
Python is executable pseudocode, Perl is executable line-noise.
next prev parent reply other threads:[~2003-08-27 4:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-19 19:09 Andreas Rottmann
2003-08-20 14:11 ` Andy Wingo
2003-08-20 15:03 ` Andreas Rottmann
2003-08-20 17:52 ` Andreas Rottmann
2003-08-27 4:26 ` Andreas Rottmann [this message]
2003-08-21 22:51 ` Kevin Ryde
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=878ypg8fvb.fsf@alice.rotty.yi.org \
--to=a.rottmann@gmx.at \
--cc=guile-gtk@sources.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).