[a / b / c / d / e / f / g / gif / h / hr / k / m / o / p / r / s / t / u / v / vg / vm / vmg / vr / vrpg / vst / w / wg] [i / ic] [r9k / s4s / vip] [cm / hm / lgbt / y] [3 / aco / adv / an / bant / biz / cgl / ck / co / diy / fa / fit / gd / hc / his / int / jp / lit / mlp / mu / n / news / out / po / pol / pw / qst / sci / soc / sp / tg / toy / trv / tv / vp / vt / wsg / wsr / x / xs] [Settings] [Search] [Mobile] [Home]
Board
Settings Mobile Home
/g/ - Technology


Thread archived.
You cannot reply anymore.


[Advertise on 4chan]


File: file.png (31 KB, 1341x154)
31 KB
31 KB PNG
systemd-analyze

post you'res
>>
i want to know if my firmware time is longer than normal people's
>>
Startup finished in 9.308s (firmware) + 5.755s (loader) + 4.035s (kernel) + 4.290s (initrd) + 3.583s (userspace) = 26.972s

could cut down the loader if i lowered the timeout value but i don't really care
running on wd blue 500gb ssd on pcie3
>>
File: 1764018047459996.png (18 KB, 809x60)
18 KB
18 KB PNG
>>
File: analyze.png (32 KB, 2168x152)
32 KB
32 KB PNG
>>108363488
>>
ty anons it seems my firmware time is generally in line
>>
Command not found.
>>
>>108363664
Mine looks bad in comparison and I have have a good pc + fast storage. Probably encryption?
>>
>>108363683
you can see what is taking long with
systemd-analyze blame
>>
>>108363488
is this ok?
>>
>>108363693
yes, thank you
>>
>>108363488
>datamining threads now asking us to run argbitrary commands and post our private TPM keys
>>
>>108363685
systemd-analyze blame

Result: JEWS
>>
File: waow.png (4 KB, 514x36)
4 KB
4 KB PNG
>>108363488
>>
>>108363488
>>
>>108363685
Thanks. Yup.. dev disk, my drives. OS drive, extra drive and another extra drive, all unlocked at boot.
>>
>>
>>108363488
ksh: systemd-analyze: not found
>>
>>108363488
>systemd
enjoy your ai slop faggot
https://github.com/systemd/systemd/issues/41085
>Claude code reviews actually got really really good recently
enjoy your ai slop you absolute fucking brain drooling retarded moron
>>
$ systemd-analyze
Startup finished in 13.868s (firmware) + 2.517s (loader) + 834ms (kernel) + 2.022s (initrd) + 2.951s (userspace) = 22.194s
graphical.target reached after 2.951s in userspace.
>>
>>108363488
>>108363636
>>108363659
>>108363664
>>108363685
>>108363693
>>108363702
>>108363735
>>108363764
>>108363840
it takes more time if the drive is encrypted
>>
File: file.png (4 KB, 429x36)
4 KB
4 KB PNG
>>108363488
>>
~ $: systemd-analyze 
Startup finished in 14.720s (firmware) + 1.389s (loader) + 2.311s (kernel) + 4.538s (initrd) + 5.366s (userspace) = 28.326s
graphical.target reached after 5.230s in userspace.

piece of shit assrock mb takes quite a while to post
>>
>>108363488
>>
Startup finished in 16.906s (firmware) + 17.797s (loader) + 715ms (kernel) + 1.641s (initrd) + 15.358s (userspace) = 52.419s 
graphical.target reached after 15.358s in userspace.

Now to be fair, this wasn't a normal boot. I resumed from hibernation. The extra 15 or so seconds in the "loader" section probably accounts for that.
>>
systemd-analyze
-ash: systemd-analyze: not found
>>
>>108363702
Lennart, no!
>>
>>108363488
Command not found.
But I timed it for you: It takes 6s for EFI to load linux my kernel directly, and another 5s for my TTY to prompt for login.
>>
Startup finished in 8.095s (firmware) + 5.742s (loader) + 745ms (kernel) + 1.989s (initrd) + 8.190s (userspace) = 24.763s 
graphical.target reached after 8.190s in userspace.

Did I win?
>>
Startup finished in 6.951s (firmware) + 394ms (loader) + 1.218s (kernel) + 31.776s (initrd) + 2.275s (userspace) = 42.616s
graphical.target reached after 2.270s in userspace.
>>
$ sudo dmidecode -t 2 | grep "Product Name"
Product Name: TUF GAMING Z790-PLUS D4
$ systemd-analyze
Startup finished in 9.824s (firmware) + 467ms (loader) + 940ms (kernel) + 1.520s (initrd) + 1.338s (userspace) = 14.089s
graphical.target reached after 1.338s in userspace.


AM4 booted faster
>>
>>108366299
no you didn't even beat me and I was concerned why my startup was so slow
>>
File: IMG_8406.jpg (126 KB, 968x1045)
126 KB
126 KB JPG
>>108363488
$ systemd-analyze
zsh: command not found: systemd-analyze
>>
>>108366642
don't make this some faggot shit, faggot
i only wanted to know shit about my system's startup
if you are a special cookie that doesn't use systemd you do you
>>
```
Startup finished in 12.531s (firmware) + 1.087s (loader) + 1.081s (kernel) + 14.120s (initrd) + 1.797s (userspace) = 30.619s
graphical.target reached after 1.794s in userspace.
```
>>
>>108366299
>openrc
>everything built into the kernel
>slow-ass early years ssd
>time from power button to login prompt is 10s
This entire thread has proven that systemd is incapable of booting fast at all. What the actual fuck? This is your "boots faster than traditional unix init?" Fucking embarrassing.
>>
Startup finished in 8.777s (firmware) + 3.459s (loader) + 17.982s (kernel) + 22.976s (userspace) = 53.195s
graphical.target reached after 22.974s in userspace.



[Advertise on 4chan]

Delete Post: [File Only] Style:
[Disable Mobile View / Use Desktop Site]

[Enable Mobile View / Use Mobile Site]

All trademarks and copyrights on this page are owned by their respective parties. Images uploaded are the responsibility of the Poster. Comments are owned by the Poster.