3 ms·
I shudder to think what you're running Windows 10 on because it only takes 2 seconds to come up on this Celeron 2957U I'm using to browse the internet.
by cptskippy 6y ago
I shudder to think what you're running Windows 10 on because it only takes 2 seconds to come up on this Celeron 2957U I'm using to browse the internet.
- Jtsummers 6y agoIf it's a corporate system like my (presently only) Windows machine then I wouldn't be surprised. They manage to configure these things so they're as fast as a Pentium 133MHz processor from 25 years ago, even though you've got an 8-core i7 with 32GB of RAM.
- cptskippy 6y agoI wouldn't either, our devs were given the standard issue Lenovo T480 which would have been mostly fine were it not for the fact that we had Raytheon ForcePoint DLP, LANDesk, Trend Micro Apex, WebSense, Cisco Amp, Cisco Umbrella, and who knows what else watching everything we did. It took upgrading to i9s to get something that could run Teams and Outlook at the same time without audio stuttering during a voice call.
- yakubin 6y agoI'm running Windows 10 on a Ryzen 5 with 16GB of RAM and an NVMe drive. Powershell takes something between 0.5 to 1 second to start. The first ~20-30 seconds after the start it feels sluggish when doing simple tasks like listing directory contents. It makes it very unpleasant to use.
- CamperBob2 6y agoSluggish behavior during and just after Windows startup is sometimes caused by mapped network drives that no longer resolve. Worth checking if you haven't already.
- yakubin 6y agoI'm talking about Powershell startup, not Windows startup.