Thanks to everyone for the info -- we're looking further into this right now.

Two quick points: first, you're only acting as an UltraPeer if you see connections labelled as "leaf" in your connections tab. If you see, say, three connections labelled as UltraPeer, that means you're a leaf (but not that you won't be an UltraPeer someday -- UltraPeers are elected as the network needs them).

Second, the CPU on startup doesn't really "count". I'm more interested on if the CPU stays that high after you've been up for a minute or so. On the database idea, that would definitely improve loading speed and is probably a good idea, but it's not our top priority right now.

Thanks very much again -- any more little tidbits would be great if people have them.

XP Pro + Limewire 2.3.4 = slow
 

to afisk :

(Or is it 2.3.3? CNET.com says so. LimeWireWin.exe Properties says 2.3.4 (File version 7.2.42.0))

1) Not running Ultrapeer (or anything other than Limewire) while CPU runs 20 to 70 averaging 30

2) Sharing 4150 files : sharing 0 files makes no difference

3) Maintaining 3 connections in the connections tab. Uploads Per Person 3, Start Upload Slots 5, Max 5

4) Cable

5) 1 GHz Athlon, 512, ASUS A7V133

The puffy XP task bar flickers, occasionally disappearing altogether for a 3 count. The machine grinds.
ONLY Limewire -- in contradistinction to whatever scenario of concurrent aps I may choose -- will dare this. Going back to 2.0.2. Which is the best of them all and who has it?

Great programme otherwise!

rems

To Adam
 

Adam,
I'm glad you're looking into these issues. For me the biggest issue is the program crashing after 30min-1hour of use. I could live with it using a lot of resources on my computer because I have them to spare, and its easy to turn limewire off. The instability of Limewire Pro is annoying though.

Is there anything I can do to help with fixing stability?

Here's part of the dump I got from a crash:

Error Signature:
AppName: javaw.exe AppVer: 0.0.0.0 ModName: jvm.dll
ModVer: 0.0.0.0 Offset: 0004643f

-----------------------

Event Type: Error
Event Source: Application Error
Event Category: None
Event ID: 1000
Date: 4/15/2002
Time: 9:43:31 AM
User: N/A
Computer: KENNEDY
Description:
Faulting application javaw.exe, version 0.0.0.0, faulting module jvm.dll, version 0.0.0.0, fault address 0x0004643f.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 6a 61 76 ure jav
0018: 61 77 2e 65 78 65 20 30 aw.exe 0
0020: 2e 30 2e 30 2e 30 20 69 .0.0.0 i
0028: 6e 20 6a 76 6d 2e 64 6c n jvm.dl
0030: 6c 20 30 2e 30 2e 30 2e l 0.0.0.
0038: 30 20 61 74 20 6f 66 66 0 at off
0040: 73 65 74 20 30 30 30 34 set 0004
0048: 36 34 33 66 0d 0a 643f..

~_~_~_~_~_~_~_

I'm running XP Pro.

-Brian

Thanks to everyone for the data. The one thing we really need to nail down is whether or not your LimeWire's are running as UltraPeers when you're seeing these numbers. Again, you can tell if your LimeWire is running as an UltraPeer by looking at the connections tab (which is disabled by default, but you can turn it on in the "View" menu). If you have connections that say "leaf", that means that you are an UltraPeer. In this case, you should see many connections (above 5 or 6). Actually, sending screenshots of the connections tab to me at afisk@limewire.com would be very helpful.

On the XP issue, I really have no idea what's going on. It's likely that there's a bug in the JVM, as there is theoretically no way for LimeWire to cause a native error like that because it's running java. What version of the JVM are you using? You might want to try a different one, like the 1.4 JVM, available from java.sun.com

Thanks again.

I'm using Sun 1.4

I emailed you

-Brian

Found a bug! Any others?
 

We found the cause of at least one of the performance/memory problems yesterday. Apparently LimeWire can slow to a crawl when sending lots of metadata (bitrates, etc.) in response to a query. This can happen in leaf or ultrapeer mode. It will typically happen to people sharing lots of files*. We're working hard on a fix and will release this in LW 2.4 in a week or two. The new version should be significantly better.

However, there are some reports that LimeWire will use too much CPU when downloading files, even when disconnected from the network. Has anyone else seen this? Try disconnecting from the network (File->Disconnect) while downloading. If the CPU usage is high, there's a problem. Any data would be most appreciated.

-Chris

*LimeWire should be able to share lots of files without any noticeable CPU impact, since it uses an efficient data structure for queries.

CPU usage still maxing out in version 2.4
 

Did this problem get fixed in 2.5, I hope?

swap under nt4 sp6
 

hello,

I have the same mistake but under nt4 sp 6 (p3 733, 128mo ram). I saw the same with another peer to peer soft called omega. they are a patch. as the same under limewire.

thanks

Geez, its all relative I suppose? DAMMIT
 

I've got a P-II 233, with IDE disk drives, and fortunately a 3COM Co-processed LAN card (does IP on the card and not on the CPU).... My CPU utilization is 0-6% while downloading with Limewire....


HOWEVER, I do notice that javaw.exe is sucking up more than 43MBs of ram, making CPU to memory searches painful, at best. I think the Limewire folks need to dump the JRE and alternative java engines for support if they want their app to remain consistantly stable and consistantly performing.


I'm not ponying up my 10 or 100 bucks without a decent rewrite of this application.

***********************************
Hey there LimeWire Developers... I think I speak for a lot of us here... Get a few more hot shot coders to address these issues, and we WILL part with our wallets.
***********************************


Regards,

John Dunham
dunham_john@hotmail.com

slow
 

PII 233... Limewire uses 90% of mine... Runnin on a T1 here at school, and not usin ultrareaper... The program has crashed on me a few times as well. The downloads are faster cause the school lowered the bandwith priority on the Kazaa protocol so limewire is what I looked to next... I would love to stay with it cause it is nice. Also, I would love to be able to scroll w/ my mouse wheel while in my library window. Anthing to fix this? Dont let 'er use so much resources, fix the scrolling thing, and I'll be an even happier camper...

Justin
allowat399@hotmail.com