--I understand why changelog is such a miserable chore!

You've got a great set-up--can you see what eats up your CPU as shown in Process Viewer?

I just started up Limewire, and weird...

[I'm also running the LW 3.5.2jum206. Stief told me that the jum verisons would not be updated for a while, however, this one came out Sept 2, so I felt I could use it and still reliably report.]

During the loading process, where it refreshes the library, my CPU processor usage for LW jumped above 100%!

Strange. Setting a refresh rate of 1 second on the process viewer, the % usage jumps from 3%-110% and everything inbetween.

[Note, everything above is before I've reached the 4k user network limit]

Just a note, I'm just running LW, Safari, and the Carracho Server and browser. Also, I'm sharing 3200 files.

Alright, after I reached the 4k user limit LW stayed at around 5-8% CPU usage. It would hit a high of around 15% and a low of .7(!)%. Every once in a while, it would jump to the high 20s, and ever once in a great while, maybe to the high 50s.

Aha! I found something. Before this point, I had been running with advanced statistics off. Once I turned it on, my average cpu usage was around 25-35%.

I tried looking at the QRP Sent thing. It *seemed* that maybe when those peaked, I had higher usage, but to be honest, I really couldn't tell. It could've easily been something else that I wasn't aware of.

I hope this is helpful to people. If not, tell me what I'm doing wrong, and I'll try to do it right. It's about midnight now *chuckles*, so I ought to turn in. Night all.

I've got 3.5.2 beta on a 1.7GHz/1GB WinXP box which seems stable with 14000 files. Mean CPU usage is < 20%. Prior to 3.5, more than 8000 files caused the app to crash after a few hours on the same system at > 50% CPU usage, but that could have been a local problem.

Update on my test:

After some 5, 6 odd hours running, when everything is minimized, my results are these:

It seems that it "wants" (however you phrase) to stay at around 6%, however, it jumps up to the fifteen and 20s (maybe once every 20 seconds). I'm refreshing at one sec in the process viewer. Also, more rarely It jumps to the 50s-80s. Can't examine anything more closely, cuz school calls, but later I shall.

FYI
With both 3.5.1-Pro and 3.5.2-Pro, I uncheck the option for "Load LW with Windows" in the installer, but a new LW icon still ends-up in the Startup folder.

how to uninstall in winxp pro

Thanks for the head's up on the startup issue. This was working at one point, but subsequent changes I made appear to have broken it. I've just fixed it here, and the fix should go out with the next beta release.

Thanks again.

Thanks for everyone's help regarding performance issues as well. We didn't really make any performance improvements in the 3.5.x series, but we certainly did not intentionally do anything that could have had a negative performance impact. I'm glad to hear that users are able to share as many as 14000 files without a significant impact on performance, though.

That's really interesting that you see difference Window redraw rates with LW versus the JUM version. Do you have the stats open in both cases? Is it possible that you're simply looking more closely at this data than before?? We continually profile the application, so we'll continue profiling to make sure we haven't introduced any new issues. We may also be able to improve performance more for big sharers down the road.

As far as how many files is too many to share, this depends on a couple of factors, including the popularity of the keywords in your files and the capabilities of your machine. 14000 honestly seems a bit high to me, but the only potential problem would be using up too much of your CPU. So, what you're happy with in terms of CPU use is the ultimate benchmark -- I would recommend sharing up to the limit of how much CPU you would like to devote to LimeWire. If that gets too high, don't share quite so many files.

Thanks again for everyone's help.