[KellyH]

Firstly, let me thank you for the great tool that is Awasu. I'm very impressed with the functionality and stability of the program. Kudos.

Secondly, let me ask why Awasu appears to require scads of CPU time. My machine is P3-500, 512MB of RAM, and when running at 'Normal' priority, Awasu seems to take 30 to 40 percent of the CPU on WinXP. I've got 16 RSS feeds that I monitor, each once per hour. At first blush, I would expect the program to be idle almost all of the time.

I recently upgraded to 1.1, and didn't notice this behavior with 1.0.

Any tips on how I can boost performance of 1.1?

Thanks!
Kelly

[KellyH]

Firstly, let me thank you for the great tool that is Awasu. I'm very impressed with the functionality and stability of the program. Kudos.

Secondly, let me ask why Awasu appears to require scads of CPU time. My machine is P3-500, 512MB of RAM, and when running at 'Normal' priority, Awasu seems to take 30 to 40 percent of the CPU on WinXP. I've got 16 RSS feeds that I monitor, each once per hour. At first blush, I would expect the program to be idle almost all of the time.

I recently upgraded to 1.1, and didn't notice this behavior with 1.0.

Any tips on how I can boost performance of 1.1?

Thanks!
Kelly

[support]

let me ask why Awasu appears to require scads of CPU time.

This is a problem that came up the day before we released 1.1 and since this bit of code is going to be reworked very soon, we decided to hack around it for the moment (and hope that no-one noticed ). Like i said,

To work around this, open Notepad and create a file called DEBUG.INI in your user's directory (e.g. C:\Program Files\Awasu\Users\YOUR-NAME) that looks like this:

Code: Select all

    [Debug]
    ChannelUpdateThreadInterval=5

Then restart Awasu. You can experiment with the value here (restart each time). Higher values will reduce the load on your CPU but will make manual channel updates a little slower to start. The default value is currently 2; setting it 5 should be fine. One of our test machines is a 500Mhz as well and setting this value to 2 worked fine but obviously your mileage varies

Apologies for the inconvenience.

[edit]
This will be fixed in the next beta, btw.
[/edit]

[support]

let me ask why Awasu appears to require scads of CPU time.

This is a problem that came up the day before we released 1.1 and since this bit of code is going to be reworked very soon, we decided to hack around it for the moment (and hope that no-one noticed ). Like i said,

To work around this, open Notepad and create a file called DEBUG.INI in your user's directory (e.g. C:\Program Files\Awasu\Users\YOUR-NAME) that looks like this:

Code: Select all

    [Debug]
    ChannelUpdateThreadInterval=5

Then restart Awasu. You can experiment with the value here (restart each time). Higher values will reduce the load on your CPU but will make manual channel updates a little slower to start. The default value is currently 2; setting it 5 should be fine. One of our test machines is a 500Mhz as well and setting this value to 2 worked fine but obviously your mileage varies

Apologies for the inconvenience.

[edit]
This will be fixed in the next beta, btw.
[/edit]

[KellyH]

To work around this, open Notepad and create a file called DEBUG.INI in your user's directory (e.g. C:\Program Files\Awasu\Users\YOUR-NAME) that looks like this:

That works great! Thanks for the awesome support!

Kelly

[KellyH]

To work around this, open Notepad and create a file called DEBUG.INI in your user's directory (e.g. C:\Program Files\Awasu\Users\YOUR-NAME) that looks like this:

That works great! Thanks for the awesome support!

Kelly

[Devilina]

Just wondering if the CPU usage issue had been fixed. I want to recommend Awasu to some low-tech types, who will be nervous about creating and saving an .ini file on their system.

I realize you are very busy, so if you have not had time to get to it yet, if you could give me an ETF, "estimated time for fix," I will hold off on sending these folks to the download page till then.

As always, thanks so much for all the work you have done! Awasu is at least head and shoulders above all the other news readers out there, which is why I won't recommend any of the others. They just don't come close.

[Devilina]

Just wondering if the CPU usage issue had been fixed. I want to recommend Awasu to some low-tech types, who will be nervous about creating and saving an .ini file on their system.

I realize you are very busy, so if you have not had time to get to it yet, if you could give me an ETF, "estimated time for fix," I will hold off on sending these folks to the download page till then.

As always, thanks so much for all the work you have done! Awasu is at least head and shoulders above all the other news readers out there, which is why I won't recommend any of the others. They just don't come close.

[support]

Thanks for the kind words

The CPU usage problem has not yet been fixed. The next beta will be released in a few days so the fix will be in the one after that. Not everyone sees this problem, BTW.

Perhaps the best thing to do would be to pre-create the INI file for them, email it to them as an attachment and tell them exactly where to save it. Don't forget to tell them that they have run Awasu at least once first (so that their directory structure will be created). They won't have to stop Awasu to save it; the new file will get picked up the next time it is run.

[support]

Thanks for the kind words

The CPU usage problem has not yet been fixed. The next beta will be released in a few days so the fix will be in the one after that. Not everyone sees this problem, BTW.

Perhaps the best thing to do would be to pre-create the INI file for them, email it to them as an attachment and tell them exactly where to save it. Don't forget to tell them that they have run Awasu at least once first (so that their directory structure will be created). They won't have to stop Awasu to save it; the new file will get picked up the next time it is run.