I'm just hoping that Java can make a uttility to lower the ammount of RAM it chews as we all know it isn't very ram efficient.

i agree with both of your points. i still feel the effects on a amd 1.3 mg processer.

you mean Gigahertz?

1.3 MHz sounds like how fast my windows works with or without LW. lol

You need to add a fast forward bar to the player. Such as the thing used in WMP and iTunes where it moves along to tell you were your up to and you can jump forward in the song. Then i would actually use the player

Hi there!

I am using Limewire on a 10mbit (->1mb/s downstream*g*) connection with a lot of paralell downloads, but even my 2.6ghz machine has a load between 2-5 on Linux.
(-> a 5ghz machine would be needed to process everything).

I've tried different JVMs (Sun client,server ; JRockIT; IBM) but the server-jvms (all except sun-client) seem all to produce more or less the same results.

so lower cpu-load is definitivly something I am really interrested in ;-)

lg Clemens

Yeah the player needs to be updated...that and startup time are probably the biggest things for me.

Totally agree here, I think nobody uses an player integrated in p2p software for more than just listen into a few files.

This all-in-one approach has several times prooven that it does not work very well...

lg Clemens

The LW player will be better in 5.0, you should see how when there is a 4.9 beta (I don't want to poil anything, but you can look at CVS commits)

Ciao

__________________
Liens d'intérêt /Links of interest:
Gnutellaforums en français /The House's rules you have to respect / First search the forum, then create a thread / Free software alternatives! - Logiciels alternatifs gratuits!/

NIO is already in alpha-tests for developers only.
There are still a fews things to correct, notably to find a way to detect that the host has no active connection (because NIO is not blocking and now LimeWire first attempts connections with UDP without waiting for a reply, nothing happens for long; there shoudl exist a watchdog to detect that some time has elapsed, so that the connection attempt is marked unresponsive; this code existed in the previous non-NIO based blocking code, but converting it to non-blocking NIO is still not perfect.

This just means that if you have no internet connection, with the alpha version, you won't get any notification with an alert box advizing to check your internet connectivity, and LimeWire stays for now indefinitely and silently in the "Connecting..." state until a connection is available. If you have Internet connected, then nothing seems bad, and Limewire is incredibly faster and uses much less CPU and memory paging to disk.

There are still some work to do to optimize the memory usage in Untrapeer mode, but the progress is still significant (for those users that have Java 1.4+; NIO is not available on MacOS Classic that just has Java 1.1.8; but MacOS Classic never qualifies to host a servent in Ultrapeer mode, so this is less a problem).

Windows users that still have Java 1.3.1 with an old version of LimeWire will really need to upgrade now to Java 1.4 to get NIO support and benefit of the improved performance.

__________________
LimeWire is international. Help translate LimeWire to your own language.
Visit: http://www.limewire.org/translate.shtml