Wold be nice, if MT v 3 could utilize Multi-core processors..
We already have support for that in v3.0 ![]()
Do you have any info on how well RouterOS v3 scales under various common operations (i.e. routing, bridging, translating, firewall etc.) on multi-core systems? Unfortunately I don’t have the spare hardware here to test this.
one CPU core is binded to an interface, so if you have 4 cores and 4 interfaces each core will work with each interface
So Here is a can of worms !!
I now have other questions..
So If I have 2 Cores and 3 Interfaces, how does it play out?
Also where do services run? IE Proxy IPSec Etc.
Things that make you go Hmmmm…
Craig
In my opinion it is not so “wormy” at all.
RouterOS kernel still use process queues and all, just that if you are processing packets from one interface, they all should be processed with the same core (to keep packets in order etc.) everything other is scheduled to other cores as different tasks, so, most free core will have to deal with other processes and other interfaces.
and i would like to add, that with one core you had all the interfaces and all the processes hanging around, so you will have speed boost one way or another, and you should feel improvements over single-core solutions anyway. ![]()
edit:
things that makes you go aha
I didnt mean “Wormy” as in code issues… ![]()
I meant “Wormy” as in you just opened a whole can of question worms and they can get very slimy and take up a lot of time rounding them up and putting them back in the can… ![]()
But I think you put them back in very well…
Craig