Thanks Andrew :) Hopefully the documentation around CHRs will increase in the near future... I know it's mostly the same as every other RouterOS device, but the unique elements of it would be good to have an official reference for. For safety's sake, we will shut down the VM, take a snapshot, increase CPU allocation, then boot up and test... then, if it becomes unstable due to CPU change, we can at least roll back to a version that has never seen more than 2 cores. -----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Andrew Cox Sent: Monday, 23 January 2017 6:16 PM To: MikroTik Australia Public List <public@talk.mikrotik.com.au> Subject: Re: [MT-AU Public] CHR scaling CPU/Memory Hi Philip, We use a bunch of these in Microsoft Azure - it should be as simple as that: shutting it down, increasing CPU cores/Memory and then restarting. - Andrew On Sun, Jan 22, 2017 at 7:49 PM, Philip Loenneker < Philip.Loenneker@tasmanet.com.au> wrote:
Hi guys,
We have a CHR with 2 CPUs which is really struggling. I haven't found any info on the Mikrotik website or forums about scaling of it. I am considering upgrading it to 8 CPUs.
a) Is there a limit to what resources we can allocate to CHRs?
b) Can you increase CPU count by simply shutting it down and allocating more in Vmware, or is there something else required?
c) Is there anything else we need to be aware of?
Regards, Philip Loenneker | Network Engineer | TasmaNet _______________________________________________ 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