Blog de Joe Freeman

I wanted to get a feel for the perceived performance difference between a PCIE P3700 and a 6Gb/s SATA drive with Windows NTFS file system operations.  What would the real-world speed difference be for moving a lot of files around on an NTFS file system? My file copy tests showed results similar to what we see in application boot tests.  Everyday operational differences are about 1/2 of what we see in benchmarks. CrystalDiskMark NVMe mode test:  The PCIE measures as 4x-5X faster in sequential reads and 3X-4X faster in sequential writes. Windows file copy:  The PCIE drive measures about 2X faster than the SATA drive. Configuration Code Used: https://github.com/freemansoft/file-copy-speed-test Copy operation: 10,000 files each of size 200KB. C: is a 600GB/s SATA drive NTFS  I: is an Intel P3700 NVMe drive NTFS Test Results The test copies 2GB across 4 different permutations.  PS C:\Users\joe\Documents\GitHub\file- copy-speed -test> .\speedtest-file-copy.ps1...

I wanted to test the relative performance of two drives on a Windows 10 machine and get a feel for how much overhead my anti-virus products cost me.  To that end, I created a program to copy in different combinations between the two drives.  I ran that test with different Anti-Malware versions and configurations  From the README.md on GitHub The Program 1. It takes the names of two directories 2. It creates the number of files that you specify of a size you specify in both of the directories passed in.     1. You want big numbers for both.  The default is 10,000 files of 200,000B each. 3. It copies the large number of files in the 4 possible source/destination pair combinations. 4. It writes the timings to the console and deletes the test files. In my case I ran a couple different variations to see what was happening 1. Drive A anti-malware enabled .  Drive B anti-malware enabled 2. Drive A anti-malware enabled .  Drive B anti-malware disab...

I foolishly decided to convert a Windows operating system drive from MBR partitioned to GPT partitioned. That conversion didn't go right. The boot portion of the drive was erased or destroyed. The partitions were still there and no data was destroyed.   I tried to convert the drive back to MBR.  That didn't work easier.  This is usually the point where you might start panicking. The cycle time is pretty long when you try and fix the boot portion of a physical disk.  There are continual physical machine restarts.  There is also risk that data will be lost while attempting to fix this. I wanted to attempt drive repair without risking destruction of data on the drive I was working on. In addition, I didn't want to work on this drive without access to the internet. My target laptop laptop has two bootable drives in it.  I realized that I could convert the trashed disk from Physical to Virtual using Paragon Drive Copy. Then I could hack on the virtual drive...