i currently have an RB493G running my home network, and it has been rock-solid stable (uptime of 332+ days as of today).
however, about a year ago i upgraded my internet connection from a 7Mbit/sec DSL connection to a 75Mbit/sec cable connection. i run some pretty minor queueing rules (not to be confused with the automatic "simple queue" function) that sets speed limits for each device on the LAN based on the subnet of the IP address i have statically assigned them.
i noticed recently that with just my computer doing something online (downloading a large file at or near max ISP speed), my RB493G's CPU usage gets maxed out at 100%, and the Profile tool shows that it is mostly the queue using the CPU cycles. i want to upgrade to a more robust solution to handle the extra speed + the queue rules, especially since i'm considering upgrading the speed again to 150Mbit/sec (or more). i'm mainly interested in the CCR1009-8G-1S-1S+PC because it is passively-cooled and will be silent while running in my home office/server room.
i know from first-hand experience at my job that certain processes within RouterOS are only single-threaded, although i'm not sure of how every process is handled, including queueing.
i need to know if there is any information anywhere that breaks down a complete list of all the processes within RouterOS, and specifies whether they are single- or multi-threaded, with the main focus at the moment being the queue rules.
if queueing is only single-threaded, then i'm wondering if a CCR1009-8G-1S-1S+PC is going to be faster than an x86-based solution (probably an old Core2Duo e8400 @ 3Ghz that i have laying around doing nothing ATM). the x86 route would most certainly be cheaper, since i already have the hardware, but i'd be willing to pay the $$$ for the CCR1009-8G-1S-1S+PC if it is going to be a faster solution for single-threaded performance, especially given the power, heat, and size advantage that it has over an x86 PC.
P.S.: i also do have a Core-i7 2600k quad-core @3.4Ghz w/hyperthreading that i could use if need be