Troubleshoot.HighCPU/nl

Hoe kan ik het CPU-gebruik van Shareaza verminderen?

Shareaza heeft veel mogelijkheden en een goede gebruikersomgeving. Maar het kan, afhankelijk van hoe je het gebruikt, je computer trager maken. De manier om dit op te lossen is door het uitschakelen van bepaalde mogelijkheden die een systeem kunnen belasten. NB: de oplossingen die hieronder worden beschreven zijn op de standaard skin gebasseerd, dus als je iets niet kunt vinden, zoals hier beschreven staat, schakel dan de skin uit.

---

• "Plan" je downloads en zoekopdrachten: Met langzamere machines is het beter om niet te veel programma's tegelijkertijd open te hebben. Hetzelfde geldt voor Shareaza en "zijn" taken. Probeer om niet meer dan 5 zoekopdrachten tegelijk uit te voeren (je kunt wel meer zoekvensters open hebben, maar gestopt) en probeer ook om niet te veel bestanden tegelijk te downloaden (15+). Dit zal de performance ten goede komen. Als je te veel downloads in het download scherm hebt, probeer er dan een paar te pauzeren. Om een download te pauzeren, klik er met de rechter-muisknop op en kies 'Pauzeer'. Je kunt de download(s) later hervatten via hetzelfde menu.

• Beperk downloads met te veel bronnen: Sommige zeer populaire bestanden kunnen erg veel bronnen hebben. Je kunt bijvoorbeeld vele duizenden bronnen vinden voor het Shareaza's installatie programma. Wanneer je zulke bestanden downloadt moet Shareaza beperkt worden om niet te veel verbindingen met bronnen tegelijkertijd aan te maken, omdat elke download-verbinding een beetje processorkracht en geheugen nodig heeft. Als dit een probleem is/wordt, verminder dan de Maximale aantal overdrachten en/of Overdrachten per bestand in de instellingen.

• Hoeveel bestanden deel je?: Als je een grote hoeveelheid bestanden aan het delen bent, bijvoorbeeld meer dan 200, dan kun je last hebben van een hoog CPU bronnen gebruik. Dit is omdat sleutelwoorden van al je bestanden verzonden worden naar jouw Hubs. Wanneer een gebruiker zoekt naar iets op het netwerk, en je hebt een bestand die overeenkomt met een of meerdere zoektermen van die gebruiker, dan wordt er een "verzoek" naar je verstuurd. Dus hoe meer sleutelwoorden (of bestanden) je hebt, hoe meer verzoeken je zult ontvangen. Hoe meer verzoeken je krijgt, hoe meer CPU-bronnen Shareaza nodig heeft om aan te kunnen.

• Hashing: Shareaza hashes files when it first sees them. This may take up CPU and hard drive usage for the first few times you run it if you have a large collection of files. The only solution is to wait it out. Shareaza knows two modes, while hashing: One mode hashes slowly, taking care not to use too much of your CPU; this is the default mode. The other mode is to hash as fast as possible, eventually consuming all CPU power and considerably slowing down all other programs. You can switch between the hashing modes in the Home Tab in the 'My Library' box. (Available only while Shareaza is hashing.)
• Shareaza verifies large downloads: Shareaza verifies every single bit it has downloaded, to be sure it didn't get bad data. For large file, this process may take a long time to complete and since this is a hashing process as well, it uses CPU power. Wait for this process to terminate.
• Firewalls: Shareaza can occasionally experience high processor usage during heavy traffic if a software firewall (like ZoneAlarm) is heavily inspecting packets. The easiest solution is to add Shareaza to the firewall's trusted list, bypassing the inspection. This is only recommended if the firewall is causing high processor usage in Shareaza.
• Close Unnecessary Windows: Things like the Security Panel can take up lots of resources if you have it open, especially if you have a lot of content in it. Just close it after you're done using it. Same goes for search windows, transfer windows, host cache, etc. Some code will be added in the future to optimize the viewing of windows, however.
• Restrain Your Search: Shareaza doesn't include a limit on how many search results you can get, so you may get so many that it will seriously effect preformance on some computers. The best things to do are either search for specific terms (therefore reducing the results) or clicking 'Stop' when you have gotten the amount of content you want. If you're done with searching, then close the search window.
• Minimize Shareaza: If you are waiting for a download to complete, or just sharing files with the Shareaza community, it is not necessary to keep Shareaza maximized all the time. Try closing all open windows you don't need (searches, transfers, host cache) and send Shareaza to the tray. If you don't have Shareaza set up that way, go to the General Options (Shareaza Settings > General > General) and configure the 'Tray' options to what you want.
• Do not run as a hub: As a hub, Shareaza will use most of its resources to maintain network traffic and hence uses a lot of bandwidth, CPU and RAM. To prevent this, force Shareaza to run as a leaf node, by disabling "Allow this node to became a hub." in the settings. Read more about becoming a leaf
• Too many security rules: If you have a huge number (>1000) of security rules in the security window (press F7 to open it), then Shareaza may use a lot of CPU time for matching every incoming and outgoing connection against those rules. Unfortunately, this code is not optimized for a huge numer of rules, yet. Using the Shareaza Security Update is no problem, you can find it on the forum.
• Disable unnecessary networks: The more networks you connect to, the more resources are required to maintain the connection to the different networks. If you don't need a network for some time, try disconnecting from it.

Windows XP Tips

You can lower system resources by turning off visual effects. To do this:

Press: Windows Key + Break (or right-click My Computer and select Properties) In the Advanced tab, click on the Performance Settings and select Adjust for best performance.

Process Priority (Windows 2000 and XP Only)

If you're using Shareaza and like to have it run in the background while you do other tasks, depending on your computer specifications you may notice annoying delays because of the level of CPU usage that the Shareaza process is consuming. This is especially true if Shareaza is currently searching the network or creating hashes of your shared files.

A solution for running Shareaza in the backround for long periods of time without serious performance degradation for other programs is to reduce the priority of the Shareaza process from Normal to Below Normal. This can be done easily from the Task Manager within Windows. To change the priority, do the following:

• Open the Task Manager by one of a couple methods: CTRL+SHIFT+ESC, right-click the taskbar and choose Task Manager, or press CTRL+ALT+DEL, then choose Task Manager.
• Go to the Processes tab and find the Shareaza.exe process.
• Right-click on the process and choose Change Priority > Below Normal.
• Read the question Windows asks and choose the response you're comfortable with.
• Close the Task Manager.

Shareaza will continue to use this priority setting until the program is restarted.

If you want Shareaza everytime to start at a lower priority, you can write a simple batch file:

@echo off cd "C:\Program Files\Shareaza\" start /BELOWNORMAL "C:\Program Files\Shareaza\Shareaza.exe"

Obvious Note: By lowering the priority of the Shareaza process, the performance of Shareaza will be decreased while other programs are running. Simple uploading and downloading of a few files shouldn't see a huge hit, but if you're hashing your files or are searching the networks, then the time to complete these activities will be increased.

Warning: While you will most likely not have any problems with changing the priority setting of a process, there is the possibility that your system may become unstable and require a reboot. It's worth noting that I have never had any problems by lowering the priority of a process.

Be careful to avoid changing the priority to anything higher than Normal. These settings will NOT give you better performance in Shareaza. Setting the priority to High or Realtime will most likely cause your system to become completely unresponsive and will require a hard reboot to regain control.