pmiboe wrote:even when Awasu is minimized, CPU usage is about 30%. Activity Log shows no action
We're still looking at this to confirm what we think is causing this but we're pretty sure it's harmless. Awasu is highly multi-threaded and the worker threads hang around waiting for a request to do something. A defensive practice we've used is that they wake up periodically to check if there's anything for them to do but they're doing this a little too frequently. Hence, what you're seeing in the CPU usage is all the worker threads waking up, seeing that's there's nothing to do and then going back to sleep. We'll address this in the next release.
pmiboe wrote:I think that while AWASU is running, other programs are a little bit slower.
All of Awasu's worker threads run at a low priority so as soon as something else needs some CPU, Awasu will back off and let them use it instead.
pmiboe wrote:Concerning memory allocation it is very interesting that Awasu allocates 45MB of RAM at the moment. 20 minutes ago it were 7 MB of RAM. In the meantime I did absolutely nothing but opening this Forum, read this thread and register as new member...
This is probably the embedded IE browser. Opening a window allocates a big chunk of memory up-front which it doesn't seem to want to release even if you close the window.
Awasu also caches a lot of stuff as it updates channels (this can be turned off but you probably don't want to since it makes Awasu run really slow). If you start Awasu and a lot of channels update, you will see memory usage go up. If you then exit and restart Awasu (so that no channels update straight away), you will see that memory usage stays low.