Additional file-copy-speedtest benchmarks show smaller than expected differences with NVMe and 600GB/s SATA

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
_______________________________________________
Creating and cleaning directories
_______________________________________________
Creating test data
Creating test data : length 200,000.00
Creating test files in c:\tmp\copy-test-source : 10,000.00 files of length 200,000.00
Creating test files in I:\tmp\copy-test-source : 10,000.00 files of length 200,000.00
_______________________________________________
Running Test
Copying 2,000,000,000.00 bytes across 10000 files from I:\tmp to I:\tmp
     11.10 sec - 180,189,499.71 characters per second
Copying 2,000,000,000.00 bytes across 10000 files from c:\tmp to I:\tmp
     13.03 sec - 153,515,983.48 characters per second
Copying 2,000,000,000.00 bytes across 10000 files from I:\tmp to c:\tmp
     20.63 sec - 96,956,814.99 characters per second
Copying 2,000,000,000.00 bytes across 10000 files from c:\tmp to c:\tmp
     19.37 sec - 103,237,977.61 characters per second
_______________________________________________
Removing test files

Synthetic Benchmark Raw Performance




Comments

Post a Comment

Popular posts from this blog

Installing the RNDIS driver on Windows 11 to use USB Raspberry Pi as network attached

Image
I do a lot of my development and configuration via ssh into my Raspberry Pi Zero over the RNDIS connection. Some models of the Raspberry PIs can be configured with  gadget drivers  that let the Raspberry pi emulate different devices when plugged into computers via USB. My favorite gadget  is the network profile that makes a Raspberry Pi look like an RNDIS-attached network device.  All types of network services travel over an RNDIS device without knowing it is a USB hardware connection. A Raspberry Pi shows up as a Remote NDIS (RNDIS) device when you plug the Pi into a PC or Mac via a USB cable. The gadget  in the Windows Device Manager picture shows this RNDIS Gadget connectivity between a Windows machine and a Raspberry Pi. The Problem Windows 11 and Windows 10 no longer auto-installs the RNDIS driver that makes magic happen. Windows recognizes that the Raspberry Pi is some type of generic USB COM device. Manually running W indows Update  or  Upd...
Read more

Understanding your WSL2 RAM and swap - Changing the default 50%-25%

Image
The Windows Subsystem for Linux operates as a virtual machine that can dynamically grow the amount of RAM to a maximum set at startup time.  Microsoft sets a default maximum RAM available to 50% of the physical memory and a swap-space that is 1/4 of the maximum WSL RAM.  You can scale those numbers up or down to allocate more or less RAM to the Linux instance. The first drawing shows the default WSL memory and swap space sizing. The images below show a developer machine that is running a dev environment in WSL2 and Docker Desktop.  Docker Desktop has two of its own WSL modules that need to be accounted for.  You can see that the memory would actually be oversubscribed, 3 x 50% if every VM used its maximum memory.  The actual amount of memory used is significantly smaller allowing every piece to fit. Click to Enlarge The second drawing shows the memory allocation on my 64GB laptop. WSL Linux defaul...
Read more

Almost PaaS Document Parsing with Tika and AWS Elastic Beanstalk

Image
The Apache Tika project provides a  library capable of parsing and extracting data and meta data from over 1000 file types.  Tika is available as a single jar file that can be included inside applications or as a deployable jar file that runs Tika as a standalone service. This blog describes deploying the Tika jar as an auto-scale service in Amazon AWS Elastic Beanstalk.  I selected Elastic Beanstalk because it supports jar based deployments without any real Infrastructure configuration. Elastic Beanstalk auto-scale should take care of scaling up and down for for the number of requests you get. Tika parses documents and extracts their text completely in memory. Tika was deployed for this blog using EC2 t2.micro instances available in the AWS free tier. t2.micro VMs are 1GB which means that you are restricted in document complexity and size. You would size your instances appropriately for your largest documents.   Preconditions An AWS account. AWS ac...
Read more