[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [albireo-dev] performance
- From: "Goering, Jon" <Jon.Goering@xxxxxxxxxxxxx>
- Date: Wed, 10 Dec 2008 10:48:55 -0500
- Delivered-to: email@example.com
- Thread-index: Acla3R6n41Zd8DoYTTecp+6xvXJtewAADE5w
- Thread-topic: [albireo-dev] performance
Thanks for the response. The various classes used in the class
hierarchy for a view were noticed by others and the question was raised.
The question was also raised if the Albireo project was still using the
same concept as the original code base. I'm not saying we are
experiencing any noticeable performance impact regarding speed in
bringing up a view; we were just curious.
From: Bruno Haible [mailto:haible@xxxxxxx]
Sent: Wednesday, December 10, 2008 10:36 AM
Cc: Goering, Jon
Subject: Re: [albireo-dev] performance
> We are using the original code base from which the Albireo project was
> started from. One sees the usage of an applet for every view under
> hood. What is the performance impact / overhead of this along with
> usage of a root and layered panes? Is this still being done for the
> latest Albireo code base?
What do you mean by "performance impact" for an interactive GUI?
The memory footprint is that each applet will have a Swing double-buffer
associated with it, while SWT controls usually are not double-buffered.
The ping-pong game of sending events between the AWT EventQueue thread
and the SWT Display's event thread certainly increases the time between
user action and the visible response. But it will not drastically
the CPU consumption. Therefore whether it counts as "performance"
on your mileage.
> The contents of this e-mail are intended for the named addressee only.
> It contains information that may be confidential. Unless you are the
> named addressee or an authorized designee, you may not copy or use it,
> or disclose it to anyone else. If you received it in error please
> us immediately and then destroy it.
Such a disclaimer is not applicable for mails that you send to a
viewable mailing list.