If a system is released in a particular time with Win7 then you'll have some trouble running it with Win10, and the older the PC the bigger the trouble.
First, drivers - it's not guaranteed that you'll find proper drivers for all hw, sometimes you'll find Win8 drivers that will work on 10, sometimes not;
Second, given the same system, Win10 is not lower on resources (beside bloatware), not even close to Win7.

I personally tested this on an old Win7 laptop.

Only, Win10 is optimized for most modern PC, it could be that you could not notice much performance difference.

 

ol skool.. my amd zacate hp laptop was built around win 7 os, upgrading it to win 10 doesn't do any better.. i only starting to enjoy win 10 when i decide to move to modern cpu..

 

Huge tech wisdom as always pal
And actually, the now famous AMD Smart Access Memory introduced in the CPU/GPU 5000/6000 series uses a bit of that PCIe4 technology. I wonder if the new consoles use it too with the SSD. They commented that in the video.
Obviously the CEO of that company is a PCIEe4 guru so they can design very amazing hardware that speed up some PCIe communication that currently very few companies can.

 

About the overprovisioning feature of SSDs using its company software I just wanted to clear some things.

It's not something that raises the speed, it's something that lowers remarkably the speed/durability worsening over the years.

Also, you don't need to run that "samsung magician" or equivalent at startup. When it's set up (SSD firmware level?) as long as you don't touch the disk partitions it remains activated.

 

English, Chinese and Mac version please

 

i will tell you i come from a prehestoric amd ahtlon 3000mhz medion crap system from the aldi
now i have a 3800x
with m.2 for windows installation
my fls projects from my old system they always run into the red 100cpu with slowest buffer
well these projects on my new system they hit 20/30% cpu load tops with 48000 24bit 5ms latency

 

mach sachen
BTW he was talkin bout a compare on equal specs machine of win7/10

 

Last edited: Dec 24, 2020

They kinda copied it from the consoles actually hehehe. Btw, just so people don't misread it please allow to rephrase what you wrote, the SAM tech is only available on Zen 3 with Radeon 6xxx series.

What @itisntreal does not probably understand, is that Win10 by default caches the files needed to boot for priority and also the most frequently opened apps as well so they launch pretty quickly. This way it sort of looks as snappier but it isn't. It is possible to do the same with Win7, only it's missing some advanced ssd support introduced with Win10. Installing Win7 on modern systems is not easy but not really difficult too if you know what you are looking for.
Let me here repeat once again that the rhumb rule to install a version of Windows on a machine is one:
If the chipset driver works then most likely everything else will work too.
Also for once more, what Intel and AMD do not mention, is that their chipset driver is compatible with every Windows version all the way back to fkn Windows XP and in some cases Windows 2000 and NT4 lol.

Hmmm... You must tell me how you came up with this brother. This is a very sensitive topic so with your permission i need to clarify a few thingies:
First of all, so people understand it once and for all, TRIM is not some mysterious "function", it is a simple command where the OS informs the ssd's controller which data blocks on the ssd's memory cells aren't used anymore so they can be wiped in the background. With TRIM enabled the OS knows exactly where that data is in the first place. Why it is needed ? Because when you delete something on an ssd, even if it's the smallest data possible, the ssd has to remove the whole block containing that data page, so it moves the rest of data contained in the particular block on a temporary buffer and it moves it back to original block after erasing what the user asked.
Secondly, as Seagate correctly mention, peeps need to understand that we measure hdd storage in gigabytes and memory in gibibytes.
We may see 500gb hdds and 64gb ram but "gb" does NOT imply the same metric unit in both cases.
The gigabyte stands for 1 million bytes whereas the gibibyte stands for (a little less than) 1.074 mil bytes.
Now although ssds are non-volatile storage so practically have the same usage as hdds, they are made of memory (nand flash ram) and accounted for as such. Therefore, ssds have actually all the extra space like normal memory mentioned in gibibytes and NOT gigabytes and this extra storage is reserved by the manufacturer to facilitate background activites like garbage collection. Note here, that this is done by the ssd's controller itself and users never see it happening as it's a background automatic operation.
To sum it, over-provisioning is just having extra space on the solid state drive so it -simply put- can perform more efficiently. Note here that the more space an ssd has the more efficient it is.
More on this, IT geeks must have noticed all these years, that typically the bigger the ssd the better it performs. Why, of course because it has more space for over-provisioning. Some manufacturers even go all the way on this and apart from the extra storage i mentioned from gibibytes metric that's already there in every ssd, they reserve more of the actual space on the ssd and sell it as a smaller capacity drive so they ensure optimum performance and also very importantly, endurance. For example, when you see someone selling a 960gb drive, that drive has actually 1074gb of storage where the 114 (40+74) extra gb are reserved for over-provisioning. A typical example is the Samsung ssd series. The most popular Evo and Evo plus models come in 250gb, 500gb, 1tb etc models. But they are actually 256gb, 512 etc etc plus they include the extra gbs as they are counted as gibibyte units and not actual gigabytes.
On a personal note, on my home's i3 comp i have a 500gb Samsung 850 Evo. I have partitioned the drive to a 420gb system drive and left the rest unallocated. A mate sat on that comp recently and saw this and said "wtf, what have you done lol ?" What my mate didn't understand is that, the ssd's controller is smarter than he thinks. It "realizes" that this space is left for extra over-provisioning and automatically leverages it for best endurance and performance. Needless to say that after 5+ years of continuous operation and countless games and apps install/uninstalls my drive is @ 99% of its life. Nuff said i guess.
By having over provisioning and TRIM, the ssd's controller redistributes the data over the ssd's cell blocks so reads and writes are as optimal as possible because by moving data across the cells makes sure that the next write will surely go to an empty block, again because on ssds in order to overwrite any data, the ssd has to wipe the existing data first. So just because the space on that block was pre-emptied, when a new write command is given, the data is written as fast as possible without the need to make that space available first and then write that data.
Therefore,what ssd over- provisioning does is:
1. It surely improves an ssd's endurance and increases its lifetime span.
2. It may improve writes by allowing TRIM, garbage collection and other background operations to perform faster due to keeping extra space on the ssd.
Lastly, as i mentioned before:
Endurance and performance, are also dependent on the ssd type and controller: SLC (non existent anymore) MLC, TLC, QLC, are all types of nand flash contained in ssds. To keep it short, a cheap QLC drive of 1TB typically has the endurance and performance of a 500gb MLC drive or a 750gb TLC drive. Why, because it writes 4 bits per cell instead of 2 an MLC drive incorporates, and 3 of a TLC drive. So because, it has LESS actual memory cells to write data on, performance and endurance suffer after enough writes or when the drive is over half full. These drives are recommended only for read purposes (eg. library disks) unless you are truly short on cash, which of course is understandable. It doesn't hurt knowing what your drive is though, so then you can treat it better
Sry for the long post, i hope now the over-provisioning and maintenance of ssds is clear,
Much love and Merry Xmas @ mate Xupito and to all of you,
Cheers :D
EDIT: Corrected a couple of numbers, long post, i got a bit careless with figures, it's fine now :D

 

Last edited: Dec 25, 2020

you deserve you own button right between love it and useful

 

on side note, I just learn today that we can install our single license win 10 as dual boot, but must be done on separate hard drive (ie. partitioning won't work). I think I like it better than virtual box because this will be using fully native resource (like CPU and ram). But I don't know cons yet,still experimenting, so far I still can access files on both drives/OS though it has different settings and program installations.. anyone has some experience to share? is it better than sharing native resource with virtual box? Cc: @SineWave et all.

Hope this not off-topic cuz maintaining ssd is on it for heavy reinstall win10 on ssd..

 

no problem with offtopic for me but maybe open a thread to get more rseponses

 

Mainly yes. Of course it depends on what's your goal here. Virtual boxes are good for testing apps but not much else when it comes to audio. Mainly because realtime performance suffers due to the added latency of the virtual box and of course the sharing of available resources/peripherals can put a toll to any comp's general performance.
Afaik, this is evident in even fast servers which are typically built to run multiple VBs at the same time but unfortunately there is no way to leverage the added audio latency. This is also one of the reasons why the industry is moving towards Ethernet audio solutions connecting multiple devices and comps into one network with very little latency.
So if you want to run Windows apps along side macOS the best way is a second comp to tell the truth. VB will allow to do some things but it's just that. On the other hand if you want to run DAW+plugs on Windows, the separate drive is the proper solution.
Also, there is always a risk of file corruption when partioning a drive between different file systems, especially when you share files between those partitions. Note here, that the main culprit here is Windows heheh, macOs and Linux are much better in this particular subject.
But this is for real installations on partitions, VBs are essentially protected sandboxes so the file corruption risk is practically non existent.
If i can add my thoughts on this, MS should put their fat asses down and give the users the file system they have been waiting for 20 years now. Fkn incompetent corporate bitches lol.
Merry Xmas

 

Last edited: Dec 27, 2020

I didn't write it in the most clear way. So what I meant was that (over-provisioning):
1. Improves durability
2. Minimizes the speed decay over time.

This is related but not the same that the Trim feature. I still didn't know several things you explained. Nice as always.

Cheers geek comrades. Okay, the rest too

True fact too. VMs were never about raw performance but convenience in the first place. Even the file I/O (both latency and speed) is a subject on its own, let alone latency with audio.
And it happens that audio leans especially well to ethernet connected slaves. Because the MIDI/audio bandwidth is quite low compared to the processing the slave audio machine does as long there's a middle to high load of VST processing there.

 

Last edited: Dec 27, 2020