As mentioned in an earlier post regarding LW (upon loading) taking up 100% pf CPU resources.
With nothing to lose, I reset LW options back to default. This meant that I had to set up LW options all over again.
Fortunately, I quickly found that by reducing the amount of files shared from my library, the % of CPU required by LW dropped to quite low amounts. (This was unforseen by me and quite a surprise) I found that when sharing about 4,500 files, (and yes, even after LW had been given lots of time to sort and load these files) CPU usage eventually stabalized at about 58% and stayed there.
When I reduced shared files to about 75, LW CPU usage stabalized at a mean of between 7 and 10% with the odd high spike, that I think is about right.
This is not good for the LW P2P community, but it works for me. I haven't attempted yet to calculate the point where amount of files shared actually pushes CPU usage up beyond acceptible limits.
I share over 5,000 files on Shareaza with no problems at all, so if my conclusions are correct, there must be a bug somewhere in LW Pro. Incidentally, I'm really interested in finding if this solution works for others or is a local thing.
Regards, KKlutzz