--- On Tue, 2/10/09, Erick Tyack <li...@acurrus.com> wrote:
> To look further into this issue, I suggest we test
> "Slow Java" with one
> or two freely available Java apps. Then create a matrix of
> results on
> wiki.ltsp.org. Benchmarking performance would be helpful
> to figure out
> the effect different solutions have on the problem.
>
> Any suggestions for a couple Java apps?
>
> I started a LTSP wiki page at: http://tinyurl.com/bppm4t
>
> If I am duplicating someone else's work, please let me
> know
>
> Thanks,
>
> Erick
>
Thanks, Erick, for your willingness to help with this.
My brother is a real high-powered Java programmer. I explained to him the
problem we are encountering. This is what he had to say:
Most likely a color mapping problem. In the old days it was a major problem
for Java to map the millions of colors on most graphics cards to the 256 that
were supported. It's hard to tell anymore but even on Windows, if you had the
color scheme set to millions of colors, Java applications ran slow and by
magic, seemed to work just fine if only 256 colors were chosen. Same problem
probably exists in the LTSP color mapping code. Any of your Java programs that
fire up a JFrame should be good for testing. Netbeans and Eclipse are both
open source Java applications.
I thought it might at least give you an idea of what to look at.
------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_____________________________________________________________________
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.freenode.net
