KB4100375 Windows 10 Insider Release Preview Build 17133.73 - Apr.10 Insider
-
All I know with an SSD, it downloads at a flat 8 MB/s until finished, with an HDD it drops after a shortish period. My hard drive will write at 80 MB/s, so it cannot be a hard drive bottleneck, the CPU is the same of course. It would be great if we could run uupdump without verifying. I wonder if we can modify the .cmd file?
It's all about access times on SSD vs HDD. While downloading with default settings and the HDD cache buffer is full the HDD has to write to 4 different locations which means the needle has to jump to 4 different locations and once the verification process starts the needle has to jump to even more locations. This slows down everything a lot.
Best would be to download to a RAM disk on really fast hardware. :)
-
-
It's all about access times on SSD vs HDD. While downloading with default settings and the HDD cache buffer is full the HDD has to write to 4Once the verification process starts the needle has to jump between 4 different locations and once a verification process starts it has to jump to even further locations. This slows down everything a lot.
Best would be to download to a RAM disk on really fast hardware. :)
Yeah - I guessed it was to do with good old cache buffers. It is a pit NVRAM is so expensive - that would be a real game changer. It is a pity we cannot skip the verification phase. I realised that the moment I sent post and edited it.
-
Yeah - I guessed it was to do with good old cache buffers. It is a pit NVRAM is so expensive - that would be a real game changer. It is a pity we cannot skip the verification phase. I realised that the moment I sent post and edited it.
Heheh, since the whole UUP mini server is just a bunch of source code, I'm certain it can be hacked to skip the verification. I would however not recommend this.
Yes, any type of RAM disk impacts performance a lot for any IO activity. The boost in performance is huge.
-
Heheh, since the whole UUP mini server is just a bunch of source code, I'm certain it can be hacked to skip the verification. I would however not recommend this.
Yes, any type of RAM disk impacts performance a lot for any IO activity. The boost in performance is huge.
Thinking abut it, I do not see how a RAM disk would gain me much as my download to SSD is maxed out at my max broadband speed and remains constant. I would only gain anything in the last 30 seconds or so whilst verification continues after downloads have been completed.
-
-
This is really slow - I and downloading at around 0.7 MB/s compared with 10 time that using GitHub.
-
This is really slow - I and downloading at around 0.7 MB/s compared with 10 time that using GitHub.
I downloaded the ESD of my edition (2.8 GB) at the same speed that I always downloaded the UUP files with the miniserver, I had no problems.
-
I also had no trouble downloading both the x86 and x64 esds (EN-US). I have made a multi-architecture ISO, a x64 ISO and I am working on a x86 ISO. Let the fun begin.
Edit: Bummer. The multi-architecture ISO with two separate Install.wim files was a mere 2.03MB to large to fit on my 8GB USB drive. I am making one with two separate Install.esd files now.
Last edited by tracit99; 03 Apr 2018 at 08:21.
-
Did a clean install of the x64 ESD (en-us), no issues whatsoever.
-
For those who like to experiment, you can use the MCT to create the ISO with the leaked XML file, you just have to download the current MCT, then put the XML file in the same folder and run this command: MediaCreationTool.exe /Selfhost
All the credits to abbodi1406 from MDL.
Last edited by LEOPEVA64; 03 Apr 2018 at 15:21.
Reason: change link
-
-
For those who like to experiment, you can use the MCT to create the ISO
with the leaked XML file, you just have to download the current
MCT, then put the
XML file in the same folder and run this command
: MediaCreationTool.exe /Selfhost
All the credits to abbodi1406 from MDL.
Thanks for the reminder of this method. 
Quote
