Hi Alex, It is complicated ;) Changing CPU is an 'expensive' process in software - if you consider each data packet as a complex data structure object in software, then to initialise and populate that object in software takes vary many CPU cycles - so every time a packet is swapped to a different CPU, then there is a 'lot' of time wasted by building up the new structure, then breaking down the prior one. If you didn't make it to the MikroTik User Meeting last month, then I highly recommend to take a look at the technical presentation by Janis Megis - it is the /second/ presentation (immediately after the 'new products' section) where Janis discusses in detail some of the challenges to maximising multi-CPU performance. As many members of this list will know already, queue performance has been a very VERY major issue with CCR for quite some time, and only relatively recent routerOS software developments have begun to make some significant improvements. So I reckon that the system default is most likely intended to keep load off the system resource unless explicitly configured to do so. If there is enough support from list members out there, I can try to get some comment from MT team about this - if it is of some interest? Cheers! Mike.
-----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Alex Samad - Yieldbroker Sent: Tuesday, 30 June 2015 11:03 AM To: MikroTik Australia Public List Subject: Re: [MT-AU Public] ccr1036
Just to know why. I would have thought multi cpu access would be better, but I am not that knowledgeable about all the different types.
A
-----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Mike Everest Sent: Tuesday, 30 June 2015 10:59 AM To: 'MikroTik Australia Public List' Subject: Re: [MT-AU Public] ccr1036
Hi Alex,
That is the default setting - I suppose that's to avoid some cpu resource hit without explicit admin action to do so?
Does it raise some kind of problem for you, or just interested to know why? :-}
Cheers!
Mike.
-----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Alex Samad - Yieldbroker Sent: Monday, 29 June 2015 10:01 PM To: public@talk.mikrotik.com.au Subject: [MT-AU Public] ccr1036
Hi
Wondering if people have played with /queue> interface print detail
On their phy interfaces ?
Mine is set to only-hardware-queue, wondering why we are not using multi- queue-ethernet-default ?
Alex
_______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com. au
_______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au
_______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au