bseklecki_ge
Member
I have a 1809/Pro with 16gb RAM, high end i5 (joke), and non-NVMe SSD; which is decent, but the OS is managed by umbrella corporation and lots of agents adding overhead.
It takes about 45min-1 hour to "load" an Win Server 2016 or Win 10 LTSC 1809 image.
It takes about 3 hours to "commit a change", but only 5/10min of that is the ISO build.
I never really see the system CPU, RAM, or I/O choked at any point though.
A lot of days I forget that its running in the background.
I assume all the OS bloat is causing my delays.
So I guess my question is: How to profile optimized hardware environment for NTLite?
Anyone building a Driver/Update integration build in less than an hour?
Limiting discussion to non-Virtualized environments:
If I switch to W-Xeon CPU Platform with bunches of Cores, will NTLite code scale on Cores?
VVMe Storage?
32gb RAM
Fewer cores, faster clock speeds?
Perhaps drugs and alcohol to dilate my perception of the passage of time?
~BAS
It takes about 45min-1 hour to "load" an Win Server 2016 or Win 10 LTSC 1809 image.
It takes about 3 hours to "commit a change", but only 5/10min of that is the ISO build.
I never really see the system CPU, RAM, or I/O choked at any point though.
A lot of days I forget that its running in the background.
I assume all the OS bloat is causing my delays.
So I guess my question is: How to profile optimized hardware environment for NTLite?
Anyone building a Driver/Update integration build in less than an hour?
Limiting discussion to non-Virtualized environments:
If I switch to W-Xeon CPU Platform with bunches of Cores, will NTLite code scale on Cores?
VVMe Storage?
32gb RAM
Fewer cores, faster clock speeds?
Perhaps drugs and alcohol to dilate my perception of the passage of time?
~BAS