I installed pop!_os as my daily driver some months ago (completely got rid of windows) and have thought it pretty good. But something about it seemed off - it would take programs just too long to open, it wasn’t snappy… Once I got into something it seemed to run fine (playing dota or something else was fine after initial quirks).
Well, today, figured it out…
When I did the first install, I was very nervous about deleting all of my existing data on my disks and so tried to manually partition everything so that I could get it right (I think I was also planning to dual-boot).
Fast forward to today, and I’m testing speeds on all the drives to see which one to pitch for a new one I acquired. I see the 3 HDDs, but where is the SSD… Oh god, I installed the boot partition and root and home all onto one of the ~12 year old HDDs and the SSD has been sitting idle.
Anyway, just about done with the new fresh install onto the SSD, hopefully it isn’t too hard to start port over the home directory from that HDD…
I never timed it up precisely, but on my desktop with an MSI board, it sometimes feels like I’m waiting longer for the board to get past the UEFI into the bootloader than for the whole OS to load off my m.2…
I love booting up servers. 95% of the boot process is spent on the ram check. 4% is spent on the actual bios things, and 1% is actually booting the OS.
Even on my home server (a desktop with 64 gigs of ram) the ram check takes longer than the OS.
I just remembered watching the RAM counter run up… in KB…
…then typing in duke3d…
Even on my home server (a desktop with 64 gigs of ram) the ram check takes longer than the OS.
I was pretty sure I messed something up when I upgraded the RAM in my desktop from 16 to 64 gigs and it wouldn’t output any signal for solid 10 seconds, lol. And the regular 5 second black screen on normal boots was still something I had to get used to coming from maybe a second with 16 GB
