You're already aware that I occasionally see the database locked problem. Also, still outstanding is the issue of read/unread (guid vs. url, etc.).
This is my current DEBUG.INI:
I currently have 149 channels. Of these I turned off updating on about 20 seldom read ones to try to reduce system load and improve performance (see below); another about 15-20 channels are plug-ins of one flavor or another.
When Awasu is not busy updating or banging on its database, interacting with Awasu is fine and I can move around, view groups, mark remaining items as read, and generally use it as expected. However, when Awasu gets busy in the background (typically 80-96% of my CPU, as shown by Task Manager), Awasu is extremely frustrating to use. The GUI essentially just stops. I don't get ghost windows like with some older versions, it's just that Awasu basically seems to ignore any mouse clicks, PageUp/Down, typing, or any other user interaction. *Sometimes* the cursor will change to the hourglass; usually it stays whatever it was before the GUI stopped (arrow or hand). After anywhere from 2-60 seconds, Awasu seems to decide to get around to me again
and the GUI is back to normal for awhile. But, once Awasu gets busy again, the same thing happens. During these busy times, I can switch to other applications and they behave fine, though depending on what I'm doing I notice that Awasu is keeping the system busy.
So, "background" performance and servicing the UI need some improvements.