This message was deleted.
# _general
s
This message was deleted.
d
Copy code
virsh list –all

virsh shutdown <CVM-Name>

virsh setmem 8G –config

virsh setmaxmem 8G –config

virsh start <CVM-Name>

virsh list –all
not sure how low you can go these days
d
8 is about min from my experience
t
Thanks all. dropping to 8 now. fingers crossed
l
Depends how many vm's you are running.
Well, that was my experience. I'm sure 8 will be fine for a small number though, I dropped mine to 12 and it ticked over quite nicely.
t
thx for the asssist. the command has changed a bit with newer version. here it is:
Copy code
root@ahv# virsh setmaxmem cvm_name --config --size ram_gbGiB
root@ahv# virsh setmem cvm_name --config --size ram_gbGiB
e
8 GB is too low in my experience, would recommend 12GB, maybe more on latest release
l
12gb was my sweet spot. Bear in mind Tom, these appliances are serving all storage and replication.
k
Doesn’t depend on the number of VMs, it depends on the services you want to run :) There’s an excellent CVM sizing doc on our portal
l
Kees , not to contradict at all but.... What does the replication between nodes?
k
Mostly the CVM CPU.. not RAM :)
l
Aaahhh okay. O would have assumed that services would need more ram the more info was needed to replicate. You can school me in January.
k
It’s just little nuances, things like dedup/ECX etc would require more RAM as we need that capacity, RF2 or RF3 are mostly coming from CPU.
l
Thanks Kees
e
Another note, keep an eye on the CPU temp, I had to urgently buy some CPU fans for my E200-8D, same for VMW btw