Tad Bittoomuch

Correct.
 
There are a ton of things that impact actual endurance. Flash type (TLC, QLC), flash architecture (BiCS vs. FG vs. TCAT), quality of the flash (FortisFlash vs. FortisMax), overprovisioning, write amplification (from workload, overfull drive), temperature including cross temperature (program to read), ECC (LDPC) and parity, SLC caching configuration (static, dynamic, size), die consistency, presence/lack of DRAM, and much more. Most consumer drives have arbitrary TBW values well below anticipated endurance.
 
From the warranty you can arrive at the drive writes per day (DWPD) value which is more closely linked with anticipated write volume. In any case, the E12 drives (and later, E16) came out with a very high TBW rating for many reasons, although one of which was to compete directly with Samsung's offerings including the 970 PRO (MLC was being phased out). There are drives with genuinely high TBW like Team's T-Create Expert which uses FortisMax (10K P/E) flash, however E12/E12S drives have come with multiple types of flash (64L, 96L, Kioxia, IMFT) so it's safe to say the TBW is arbitrary.
 
Personally I would rate the BiCS the E12 drives originally used as some of the worst flash on the market for endurance.

You could be write (ha ha).  It's hard to tell from the product pages how many flash chips are on them because of the stickers and heatsinks covering them up.

This is incredibly unfortunate.  My server was in SBG2 and is completely gone.
 
I do however have backups, so I still have all my data.
My condolences to those who had production and/or backup servers in SBG2 😞

Edit:  A potential cause of the fire could be attributed to some defected power cables.  It seems the same day of the fire, a task was entered in their ticket tracking software to replace all the power supply cables in another datacentre.
http://travaux.ovh.net/?do=details&id=49017
It's possible they didn't get to them all in time ¯\_(ツ)_/¯
 
Press Release 1:
https://linustechtips.com/topic/1313943-ovh-cloud-suffers-major-fire-in-strasbourg-datacenter/?do=findComment&comment=14549259
 
Press Release 2:
https://linustechtips.com/topic/1313943-ovh-cloud-suffers-major-fire-in-strasbourg-datacenter/?do=findComment&comment=14551368
 

Edit: It wasn't the power cables.  At this stage it looks like the failure of 2 UPSs was the cause of the blaze.
https://www.ovh.com/fr/images/sbg/Octave-Klaba-speaking-en-vid.mp4

This is incredibly unfortunate.  My server was in SBG2 and is completely gone.
 
I do however have backups, so I still have all my data.
My condolences to those who had production and/or backup servers in SBG2 😞

Edit:  A potential cause of the fire could be attributed to some defected power cables.  It seems the same day of the fire, a task was entered in their ticket tracking software to replace all the power supply cables in another datacentre.
http://travaux.ovh.net/?do=details&id=49017
It's possible they didn't get to them all in time ¯\_(ツ)_/¯
 
Press Release 1:
https://linustechtips.com/topic/1313943-ovh-cloud-suffers-major-fire-in-strasbourg-datacenter/?do=findComment&comment=14549259
 
Press Release 2:
https://linustechtips.com/topic/1313943-ovh-cloud-suffers-major-fire-in-strasbourg-datacenter/?do=findComment&comment=14551368
 

Edit: It wasn't the power cables.  At this stage it looks like the failure of 2 UPSs was the cause of the blaze.
https://www.ovh.com/fr/images/sbg/Octave-Klaba-speaking-en-vid.mp4

That's typical of any hosting provider, it's a supply of services not disaster protection plan with it. So unless the service you are paying for is Geo-Replicated, which is generally a premium option upgrade, it's on the customers to implement data protection. And even then replication is not backup, neither are snapshots and replicated snapshots that live in the primary storage bucket/array.
 
Even if you are using a DRaaS offering the service itself does not include DR or backups, it's a service you use to implement in to your architecture design to create a DR strategy and operational procedure.
 
This is the difference between High Availability (HA) and High Resiliency (HR), what you're getting is only HR unless you have purchased an HA option like Geo-Replication, which still excludes backup.
 
It's these specific, but very important, details that often get overlooked and not properly considered with the current trend to move services in to the Cloud and this issue is compounded by Software as a Service and Platform as a Service offerings as you have no idea if DR and backups have been architected in to them at all and worse there may be no way to integrate in with backup software or some other process to extract data out regularly for backups. Sometimes things are cheaper because you are functionally getting an inferior service compared to what you had before.

I had a similar problem at the end of 2019.  I enabled DOCP, using my motherboard's release bios.
 
 
It was stable for a few months, but I'd occasionally get increasingly frequent memory related bluescreens.  This annoyed me so much that I ran Memtest for 24 hours and got a handful of errors.
 
I fixed it by leaving DOCP enabled, but reducing the memory frequency to 3200MHz and the FCLK to half of that and it was stable once again.
 
(Keep in mind this is still on the release BIOS)
 
I watched a video or read something and the idea occurred to me to update the motherboard's BIOS, which I did.  I reenabled the 3600MHz memory frequency and increased the fclk to 1800MHz and I haven't had a bluescreen since.
 
If you are going to update your motherboard's BIOS, be careful and make sure it's the bios for the same model of motherboard.  Being fairly new, your motherboard is likely to have two BIOSes which will save you in the event of a disaster.

Contained within are links to all the blog posts from the event, in which are links to each day's spreadsheets:
Day Zero: Users List
Day One Stats
Day Two Stats
Day Three Stats
Day Four Stats
Day Five Stats
Day Six Stats
Day Seven Stats
Day Eight Stats
Day Nine Stats
Day Ten Stats
Day Eleven Stats

Love it when all the slots are filled!
 

 
For those wondering:
3950x x2
5700XT x2
4790K
R9 280X
R9 270X
GTX 750 Ti

Love it when all the slots are filled!
 

 
For those wondering:
3950x x2
5700XT x2
4790K
R9 280X
R9 270X
GTX 750 Ti

Love it when all the slots are filled!
 

 
For those wondering:
3950x x2
5700XT x2
4790K
R9 280X
R9 270X
GTX 750 Ti

Just wanted to let you know...

Got my GPU passthrough working on my ESXi host. Wasn't that hard at all once I realized why I couldn't load the driver...
 

 

 

 

 

Seems that nvidia cards work on ESXi with some trial and error - at least they did ages ago
https://www.reddit.com/r/nvidia/comments/5m07h2/pci_passthrough_in_esxi_for_consumer_nvidia_cards/

You definitely don't always need the enterprise GPUs for at least proxmox, I've seen plenty of people able to pass through stuff like 1060s.
Proven to work with the newer 5xxx/xt gpus on proxmox as well as unraid.
I've seen a few people using the RX4xx/5xx GPUs on it as well.

I might be able to save you some headache.
To pass through a GPU with ESXi you need:
 
a) an Nvidia enterprise licence and
b) professional GPU (ESXi doesn't have drivers for consumer GTX/RTX cards)
 
Also as far as I'm aware, it won't work at all with AMD gpus.
 
Source: I asked a a friend who works with VMware/ESXi every day and knows about this stuff
 

I might be able to save you some headache.
To pass through a GPU with ESXi you need:
 
a) an Nvidia enterprise licence and
b) professional GPU (ESXi doesn't have drivers for consumer GTX/RTX cards)
 
Also as far as I'm aware, it won't work at all with AMD gpus.
 
Source: I asked a a friend who works with VMware/ESXi every day and knows about this stuff
 

Nice!  I love seeing others with ESXi on intel NUCs.  I myself have an ESXi NUC with an 8259U with...
 
*pauses to double check*
 
... 16 virtual machines, 21 vCPUs and between 0.1 - 0.5 %RDY depending on the vm 

running ESXi 6.5 on my i7 NuC. Works like a charm and has 4 or 5 vMs running on it

Not at all!  4 hours seems reasonable, I've (personally) seen Work Units that are expected to take between 1-2 days on older pentiums and celerons.
 
This is on the F@H FAQ page regarding minimum recommended system requirements:
Essentially if your computer is anything newer than a Pentium 4 it should be okay for Folding.
 
The only potential drawback of using slightly older/slower hardware is that you won't get as many points in the QRB (Quick Return Bonus) for submitting the Work Units more quickly.
If you're interested, have a read of some of the topics in the left hand sidebar of https://foldingathome.org/support/faq/

Don't worry, if you set the Web Control to fold for 'Any Disease', you'll get Covid-19 work units.

Not at all!  4 hours seems reasonable, I've (personally) seen Work Units that are expected to take between 1-2 days on older pentiums and celerons.
 
This is on the F@H FAQ page regarding minimum recommended system requirements:
Essentially if your computer is anything newer than a Pentium 4 it should be okay for Folding.
 
The only potential drawback of using slightly older/slower hardware is that you won't get as many points in the QRB (Quick Return Bonus) for submitting the Work Units more quickly.
If you're interested, have a read of some of the topics in the left hand sidebar of https://foldingathome.org/support/faq/

I had one of these Work Units queued, the upload took ages - estimated points dropped from about 115,000 to around 96,000
 
05:38:56:WU02:FS01:Sending unit results: id:02 state:SEND error:NO_ERROR project:11776 run:0 clone:14104 gen:2 core:0x22 unit:0x00000005287234c95e74331f0c34550c 05:38:56:WU02:FS01:Uploading 49.92MiB to 40.114.52.201 05:38:56:WU02:FS01:Connecting to 40.114.52.201:8080 05:39:18:WARNING:WU02:FS01:WorkServer connection failed on port 8080 trying 80 05:39:18:WU02:FS01:Connecting to 40.114.52.201:80 05:39:18:WU02:FS01:Upload 0.13% ~snip~ 06:17:57:WU02:FS01:Upload 99.90% 06:18:34:WU02:FS01:Upload complete 06:18:35:WU02:FS01:Server responded WORK_ACK (400) 06:18:35:WU02:FS01:Final credit estimate, 95883.00 points 06:18:35:WU02:FS01:Cleaning up Well at least that's over

Ah whoops, sorry, I must have misread/copied&pasted the wrong IP address.
 
I did have issues with 40.114.52.201 though, I have a work unit that's been waiting to upload to that collection server for at least a day now.  That's when I pinged it and saw it was down ¯\_(ツ)_/¯
 

This is a common issue if you use Chrome.  The temporary fix is to use http://localhost:7396 or incognito mode (both in Chrome) or use a different browser such as Edge or Firefox.
 

This is because the F@H servers are being bombarded with requests for new Work Units, there isn't enough to go around.
Also your GPU won't fold unless you have the folding power setting set to at least medium or high.

This is a common issue if you use Chrome.  The temporary fix is to use http://localhost:7396 or incognito mode (both in Chrome) or use a different browser such as Edge or Firefox.