CPU usage is at 20% until we open "Queues" in winbox then the CPU usage goes to 45%. If we edit a Queue the CPU goes up 60%. When we apply the queue the CPU goes to 100% for about 5 seconds before it drops to 60%. When we close the Queue it drops to 56% If we close the Queue list then the CPU goes to 45-50% and will stay there until we close winbox. When we reopen winbox it's back to 20%. This can be observed from another pc logged in under admin account watching the resource window in winbox. If the observer follows the same pattern they to get the same result with the CPU usage going up and not coming back down until you close winbox. This can also be charted via dude watching cpu usage via snmp. We have not had this problem in past versions. This is on a Router OS with AMD Athlon 2800+ and 1GB of RAM. 843.8MB out of 940MB RAM Free. HD is 307.0 GB out of 307.6 HD Free.
The more changes to Queues you make and the longer you stay logged in once a change to Queue is made the worse the problem gets. The CPU eventually maxes out at 100% and our dude server can not get SNMP response until the user who made the changes closes winbox. If you login and browse around with out opening Queues and making changes to a queue the CPU stays at 20% as normal.
Anyone else have this problem?