sooo slooooow zzzzZZZZZzzzzz
 

Slow you say? No kidding. In Napster I used to make it up to 120kbps and I wouldn't bother if it was any less than 30 or 40. I am using LimeWire and had one connection that gave me 60 but almost everything else is crawling along at a paltry 10 on rare good days and below 5 on the rest. Any suggestions? Other than moving on over to downtown L.A. that is.

Thanks

(Sorry for not trying out any of these cool smilies.)

That's too bad. :D

Adam

Thanks for taking the time to reply. (Yes, thank you too unregistered guest ;-). I have considered all the points you raise in it (and yours too unregistered guest ). I have studied the situation for three hundred some downloads from Gnutella and thousands from Napster. Overall I did notice a large speed difference and in the end I thought I'd run my observation by the very knowledgable folks in this forum (yes, you too, unregistered guest) just in case the reason for the slowness is somehow a result of the setup at my end.

By the way, I would like to make my entire mp3 collection available - that's some 4000 mp3's - but when I do that my pc kinda grinds to a halt because the processor usage maxes out a lot. This couldn't be caused by the fact that I am still hacking around on a Pentium running at 233MHz which is nearly as old as the pyramids, could it now?

Thanks again. Oh, and don't get me wrong, I like LimeWire. I recommend it whenever I get a chance.

kurt

ehhhh...what nice OS are you running?

Axe

Win98SE. Why?

Well, just askin'....the network implementation of the MS-DOS world is known as being slow.

on the other hand, in most cases the counterpart from which you download is the more important part :-)

For sharing files, also a file system that was originally developed to organize 180k-Floppy disks can not match the capabilities of a more server oriented system. If you have a free partition, try a Linux with Reiser-fs or something similar.

Success!
Axe

(dont get me wrong - i dont want to start an OS-thread here. I'm just interested in your mp3's <eg> )

Kurt-

In response to your point about sharing large numbers of files, we will be making some slight tweaks to this code for the next version of LimeWire.

The code for searching through your files is quite optimized. Do you know if you only experience a slowdown at startup when sharing large number of files, or do you experience sluggishness even after running LimeWire for, say 20 minutes? It hopefully should only be slow at the very beginning, and we are having another look at this section of the code.

There may be a slight delay in the next release, but we will be coming out with a new version quite soon.

limewire slow on mac
 

I recently downloaded limewire for mac(I have an imac - G3 with OS 9.0) and find it runs incredibly slow, even if I keep it running for over an hour! Thought it was a problem on my end as well, but increasing the memory,closing other apps, or reconnecting didn't work. I have dsl so it's not the connection. Can't be bothered to listen to my imac grind in pain anymore, so I won't be using it(limewire that is). Thanks for listening, if anyone can offer help, I'm willing to try.

Slooooooooooooooooooow on Mac
 

I too am trying to join the fun, but am having trouble with limewire on my mac. It can take my computer (system 9, g3 350 mhz, 150+ mg of ram, cable modem) forever to respond to any command when limewire is running. Like 30 seconds to a minute. Forget typing in the search field, I can't even switch to the finder, or open a folder on my desktop without a 30+ second delay. Even tried un and re installing. No dice. No trouble like this before with Napster, etc.

Any suggestions?

Thanks.

Check your Java-version - should be MRJ 2.2.4.

Got OS 9.1?? If not, you might get it.

I also have freezes and stuff, but sometimes it works up to 3 hours without crashing or so....

good luck

The LimeWire installer will automatically install MRJ 2.2.4, so the MRJ version should not be an issue.

The underlying problem here is that the MRJ is simply not very good. We have also had a great deal of difficulty reproducing these freezes internally.

If people have a chance, they could help us debug this problem by holding down the control key until a console window appears as they open LimeWire. Holding down the control key will cause a popup menu to appear when you click on the LimeWire icon. If you select the "Open" option from the menu and continue to hold down the control key, eventually a console window will appear just before LimeWire starts.

This console window will report any debugging output while you are running LimeWire. It may send you error messages particularly when LimeWire freezes.

If anyone who tries this out could report the errors they find back on this forum, that would be a great help.

More on the slooooow mac
 

Adam,

Thanks for the input. I have tried to use the java console to get more info, but did not see anything there before the software got too slow and I quit.

I can tell you that the response delays do not occur unless I am actually connecting or connected to the network. If I am disconnected, there are no issues.

Also, I would not use the word crash, as the software does not acutally seem to cease functioning. For me, it seems like the CPU is suddenly so loaded with instructions that it is unable to process keyboard or mouse input until it works its way down the stack. You type, nothing happens for a very long time, and then the text slowly appears in the field. I don't think that it is actually generating any java errors, because your commands will eventually be executed if you don't mind waiting a few minutes.

Are there any other system settings I can check? I did upgrade from 9.04 to 9.1 without effect. I increased limewire's memory allocation to 20,000 k; nothing. I am running with virtual memory and the ram disk off.

Hope that helps.

Thanks very much for the reply.

I did a little bit of my own testing over the weekend, and I was able to find some interesting results. Unfortunately, there's not a whole lot you as a user (or even me as a programmer) can do about this.

The underlying problem seems to have to do with the Mac "Java Virtualy Machine" not recycling its memory efficiently. I am going to increase the default memory allocation for the next release, but I am not confident that this will improve the situation very much. I do not believe that the user configurable memory settings actually affect the memory allocation to the JVM, but I am not sure on this.

The best that you can probably do is to try to use as little memory as possible within LimeWire. You can do this through techniques such as not running searches that will return thousands of results (using more specific search terms than "B**tles," for example) and pressing the "Stop" button when you have enough results. Killing old search tabs should also free memory. You can also reduce your number of connections in the "Connections" tab to 2. This will not dramatically decrease your search results, and it should improve performance.

Finally, not sharing huge numbers of files should decrease the necessary memory.

As I have mentioned elsewhere, the OSX version of LimeWire should be significantly better. We will also be releasing a new OSX version with LimeWire 1.5 with a much smaller download size and a new look.

Thanks again for your help.

Thanks Adam.

Limiting my connecitons to 2 seems to help a great deal. Still slow at times, but finally useable.

Out of curiosity, if I wanted to try changing the JVM's memory settings, where would I do this?

Thanks again.