384 may be good
enough.
Regards.
From: Wei ZHOU
Sent: Monday, February 12, 2024 13:00
To: Rohit Yadav
Cc: dev
Subject: Re: Discussion: CloudStack upgrade to JRE17 and Debian12/python3
Hi Rohit,
Thanks. I will revert the changes then. If the users think 512MB will lead to
large memory cons
; I would advise we should move to 512 MiB.
>
> Regards.
>
>
>
>
>
> --
> *From:* Wei ZHOU
> *Sent:* Friday, February 9, 2024 4:14:06 PM
> *To:* Rohit Yadav ; dev <
> dev@cloudstack.apache.org>
> *Subject:* Re: Discussion: Cl
I would advise we should move to 512 MiB.
Regards.
From: Wei ZHOU
Sent: Friday, February 9, 2024 4:14:06 PM
To: Rohit Yadav ; dev
Subject: Re: Discussion: CloudStack upgrade to JRE17 and Debian12/python3
Hi Rohit,
I tested the VRs of a VPC (with 2 tiers
* dev@cloudstack.apache.org
> *Cc:* Wei ZHOU
> *Subject:* Re: Discussion: CloudStack upgrade to JRE17 and
> Debian12/python3
>
> +1 option 2 (Debian12).
>
> I think we need to do a bit longer term testing before we decide on the
> new RAM size for the VR.
> 384MB might
: Discussion: CloudStack upgrade to JRE17 and Debian12/python3
+1 option 2 (Debian12).
I think we need to do a bit longer term testing before we decide on the
new RAM size for the VR.
384MB might be good to boot, but the slightest memory leak or a
temporarily spiky conntrack table could derail it
+1 option 2 (Debian12).
I think we need to do a bit longer term testing before we decide on the
new RAM size for the VR.
384MB might be good to boot, but the slightest memory leak or a
temporarily spiky conntrack table could derail it.
..But yeah, need to be conscious of the overall memory over
Hi Rohit,
Thanks for your reply.
Indeed the memory consumption could be an issue, especially for the users
who have thousands of virtual routers.
I have tested the debian12 systemvm template several times. Every time I
get an error "kernel panic" if the memory is 256MiB (the current memory
size
Hi Wei, all,
Thanks for the thread, I've no objections to either of the options, but option2
is preferred as Debian 11 security will EOL mid of this year. So, if not in
4.20, eventually we'll need to migrate systemvmtemplate base OS to Debian 12 at
some point in future.
The bigger implication
