You are not logged in.
I have 128 gigs of ram, and I'm pretty sure that's the major bottleneck in my boot times. Is there a means of configuring the kernel to only initialize so much ram during boot, and bring the rest online after booting has finished?
Offline
I highly doubt that to be an issue. Check with
systemd analyze critical-chain
sudo journalctl -b
on whether you find something to be more likely, like a visible time gab in relevant journal entries or services that actually delay you.
Offline
I highly doubt that to be an issue. Check with
systemd analyze critical-chain sudo journalctl -b
on whether you find something to be more likely, like a visible time gab in relevant journal entries or services that actually delay you.
My understanding is addressing all of that ram takes significant time. I don't know how much can be done with the kernel considering stabilizing that ram is done by the bios first.
Offline
You can use mem=nnKMG /memmap parameters to define what the kernel sees where, and if it's just about a test to check whether this is an issue you could probably just opt for a smaller mem= value.
I do doubt whether that will actually be notable towards system boot time.
Offline
You can use mem=nnKMG /memmap parameters to define what the kernel sees where, and if it's just about a test to check whether this is an issue you could probably just opt for a smaller mem= value.
I do doubt whether that will actually be notable towards system boot time.
Probably only matters for the bios. I added a good 15 seconds going from 64GB 3200 ram to 128GB 2400 ram. (can't run it at max speed, which is equivalent)
Offline
The BIOS typically provides a fast boot option (that's not windows fast boot!) which will skip an initial memory test (by the BIOS)
It's unlikely that more RAM makes the kernel itself boot slower.
Offline
The BIOS typically provides a fast boot option ... which will skip an initial memory test (by the BIOS).
I have a feature turned on to get my ram stable. I think it's Asus's performance tuning mode 4 or something. Wish I knew what it did. My current memory controller is too weak to support 128 gigs at 3200 speeds, even with severely loosened timings. Dropped bandwidth a lot and tightened timings as much as I could.
In general I'm always looking for little tweaks to boot a bit faster, though.
Last edited by zerophase (2021-02-20 21:39:23)
Offline
What board in particular?
Check "sudo dmidecode"
However, time that is spent before the kernel starts cannot be cut by anything you do to the kernel.
=> When do you lose the time?
https://bbs.archlinux.org/viewtopic.php … 0#p1957460
Offline
And forget about the 3200 vs 2400 speed difference. You won't notice that on boot times let alone 15 seconds difference.
Are you sure we are talking about 128GB and not 128MB?
Last edited by Maniaxx (2021-02-21 00:29:08)
sys2064
Offline
What board in particular?
Check "sudo dmidecode"However, time that is spent before the kernel starts cannot be cut by anything you do to the kernel.
=> When do you lose the time?
https://bbs.archlinux.org/viewtopic.php … 0#p1957460
Rampage V Extreme
And forget about the 3200 vs 2400 speed difference. You won't notice that on boot times let alone 15 seconds difference.
Are you sure we are talking about 128GB and not 128MB?
128 gb.
Offline
However, time that is spent before the kernel starts cannot be cut by anything you do to the kernel.
=> When do you lose the time?
https://bbs.archlinux.org/viewtopic.php … 0#p1957460
Offline