Apparently Intel has no intention to change there CPU architecture to create a CPU without the Spectre vulnerability so they still intend to produce and ship CPU's which are broken by design: https://lkml.org/lkml/2018/1/21/192
Let us hope every review of Intel CPU's in the future are made with...
It's actually a very clever approach since the Ubuntu kernel used is the LTS branch providing 5 years of support. A kernel from Debian, at the time the decision was made (before Debian LTS), was only supported for the time a Debian stable was living plus 1 year. With current Debian LTS that...
It is a lot easier to simply do: sudo apt install intel-microcode, on every proxmox node since microcode patches must be applied on every reboot and not all patches can be applied to a booted system, eg. a boot is required. See https://wiki.debian.org/Microcode
Hi all,
The following is a mixture of facts and speculations but never the less in my opinion means a paradigm shift for the virtualization industry!
First the facts:
1) Virtualization as a driving factor first began in this decade
2) According to Intel any CPU before 2011 (Westmere) is not...
Since your disks in the RAID are all SSD I would remove the log and cache. In your setup it could easily reduce your performance. As a general rule of thump: Unless your log device is given at least 4-5 times the random performance over your disks in the array it often only reduces the overall...
I am running with AMD Opteron processors so the newly released kernel are almost useless unless changing boot settings. This information might have come handy in the release notes! Now I will have to rescheduled a new reboot :-(
I you consider your customers data of just modest value you would behave professionally and upgrade your hardware instead of gambling with the validity of there data!
This must by far be one of the worst advices ever given!
disable sync: Do not honour sync requests from applications and instead give applications the impression that data is safely persisted. I hope no database server is running on this disk
disable checksum: Effectively break ZFS' self healing...
I have been in the same situation at work with our new HCI SAN where each node contains 1 TB of RAM and since each node contains 25 TB storage it requires a large part of the storage to make the test;-)
Another comparison:
SuperMicro MB, 2 mirrors striped 4xWD red 1TB (RAID 10) and Intel DC s3510 as SLOG on OmniosCE omnios-r151022
$ sudo zfs create vMotion/test
$ sudo pveperf /vMotion/test/
CPU BOGOMIPS: Not available
REGEX/SECOND: 1148085
HD SIZE: 510.56 GB (vMotion)...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.