I would like my linux to run faster, my laptop is a super laptop

Hi I started using manjaro, at first I was having a hard time, I was waiting for 2 minutes to open the same way, and now I got to work very well, could I make it go faster? for example a Macbook pro? that is, when I open the laptop, it automatically opens to run my kernel faster, much faster!
Thanks for your time!

If your laptop needs two minutes to boot Manjaro, then there's something wrong. My desktop computer here ─ with an 8th-generation Intel i5 ─ boots to the SDDM login screen in 10 seconds, and from login to the Plasma desktop in less than 2 seconds.

Please provide more information about your setup, as per the instructions in the quoted post below.

How to provide good information in your posts

this is my laptop, but now after many changes it no longer opens in 2 minutes, it now opens so I have it in 10 seconds but I want it even faster, can it?

  Host: zone Kernel: 5.3.15-1-MANJARO x86_64 bits: 64 compiler: gcc 
  v: 9.2.0 
  parameters: BOOT_IMAGE=/boot/vmlinuz-5.3-x86_64 
  root=UUID=f8d6459d-0769-488c-9918-06fd9b9101a9 rw quiet apparmor=1 
  security=apparmor resume=UUID=cff2ccd2-5d54-4619-81dc-ae16d2ed1249 
  Desktop: KDE Plasma 5.17.4 tk: Qt 5.13.2 info: latte-dock wm: kwin_x11 
  dm: SDDM Distro: Manjaro Linux 
  Type: Laptop System: LENOVO product: 81EV v: Lenovo ideapad 530S-15IKB 
  serial: <filter> Chassis: type: 10 v: Lenovo ideapad 530S-15IKB 
  serial: <filter> 
  Mobo: LENOVO model: LNVNB161216 v: NO DPK serial: <filter> UEFI: LENOVO 
  v: 7PCN35WW date: 09/25/2018 
  ID-1: BAT0 charge: 31.2 Wh condition: 44.5/45.5 Wh (98%) volts: 7.8/7.7 
  model: CPT-COS L17C4PB0 type: Li-poly serial: <filter> 
  status: Discharging 
  Topology: Quad Core model: Intel Core i5-8250U bits: 64 type: MT MCP 
  arch: Kaby Lake family: 6 model-id: 8E (142) stepping: A (10) 
  microcode: CA L2 cache: 6144 KiB 
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
  bogomips: 28808 
  Speed: 796 MHz min/max: 400/3400 MHz Core speeds (MHz): 1: 800 2: 800 
  3: 800 4: 800 5: 800 6: 800 7: 800 8: 800 
  Vulnerabilities: Type: itlb_multihit status: KVM: Split huge pages 
  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, 
  SMT vulnerable 
  Type: mds mitigation: Clear CPU buffers; SMT vulnerable 
  Type: meltdown mitigation: PTI 
  Type: spec_store_bypass 
  mitigation: Speculative Store Bypass disabled via prctl and seccomp 
  Type: spectre_v1 
  mitigation: usercopy/swapgs barriers and __user pointer sanitization 
  Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional, 
  IBRS_FW, STIBP: conditional, RSB filling 
  Type: tsx_async_abort status: Not affected 
  Device-1: Intel UHD Graphics 620 vendor: Lenovo driver: i915 v: kernel 
  bus ID: 00:02.0 chip ID: 8086:5917 
  Device-2: NVIDIA GP108M [GeForce MX150] driver: N/A bus ID: 01:00.0 
  chip ID: 10de:1d10 
  Display: x11 server: X.Org 1.20.6 driver: intel compositor: kwin_x11 
  resolution: 1920x1080~60Hz 
  OpenGL: renderer: Mesa DRI Intel UHD Graphics 620 (Kabylake GT2) 
  v: 4.5 Mesa 19.2.7 compat-v: 3.0 direct render: Yes 
  Device-1: Intel Sunrise Point-LP HD Audio vendor: Lenovo 
  driver: snd_hda_intel v: kernel bus ID: 00:1f.3 chip ID: 8086:9d71 
  Sound Server: ALSA v: k5.3.15-1-MANJARO 
  Device-1: Intel Dual Band Wireless-AC 3165 Plus Bluetooth 
  driver: iwlwifi v: kernel port: 4040 bus ID: 02:00.0 chip ID: 8086:3166 
  IF: wlp2s0 state: up mac: <filter> 
  Local Storage: total: 476.94 GiB used: 60.76 GiB (12.7%) 
  ID-1: /dev/nvme0n1 vendor: Western Digital 
  model: PC SN520 SDAPMUW-512G-1101 size: 476.94 GiB block size: 
  physical: 512 B logical: 512 B speed: 15.8 Gb/s lanes: 2 
  serial: <filter> rev: 20210001 scheme: GPT 
  ID-1: / raw size: 278.32 GiB size: 272.95 GiB (98.07%) 
  used: 49.14 GiB (18.0%) fs: ext4 dev: /dev/nvme0n1p1 
  ID-2: /home raw size: 146.48 GiB size: 143.19 GiB (97.75%) 
  used: 11.01 GiB (7.7%) fs: ext4 dev: /dev/nvme0n1p2 
  ID-3: /opt raw size: 31.25 GiB size: 30.63 GiB (98.03%) 
  used: 580.9 MiB (1.9%) fs: ext4 dev: /dev/nvme0n1p6 
  ID-4: swap-1 size: 17.58 GiB used: 42.0 MiB (0.2%) fs: swap 
  swappiness: 60 (default) cache pressure: 100 (default) 
  dev: /dev/nvme0n1p3 
  System Temperatures: cpu: 37.0 C mobo: N/A 
  Fan Speeds (RPM): N/A 
  Processes: 255 Uptime: 4d 21h 17m Memory: 15.43 GiB 
  used: 4.14 GiB (26.8%) Init: systemd v: 242 Compilers: gcc: 9.2.0 
  clang: 9.0.0 Shell: bash v: 5.0.11 running in: konsole inxi: 3.0.37 

No, not really ─ at least, not with a laptop. The boot-up time is always going to be around 10 seconds in Manjaro ─ which is already blisteringly fast, considering that many distributions really do need 2 minutes to boot up, and sometimes even more.

How did you measure it?
Timer from you push the power button?
With the systemd-analyze tool?

but i have a macbook pro since 2011 and its weaker than the laptop i sent it to, and that macbook works better. Thanks for your time

that's how I measured it
The stopwatch from you presses the power button.

I'm not sure whom you're addressing, so in case it is myself, then that's 10 seconds between pressing Enter at the GRUB screen and the SDDM login screen appearing, as measured on a clock.

No stopwatch, no software measurement, and no hardware initialization time included. :slight_smile:

Define "works better"?

1 Like

Try what is written here https://wiki.archlinux.org/index.php/Improving_performance/Boot_process
Don't compare with the MAcbook, it is probably not shutting down but suspends to RAM or to disk.


In that case, you also measure the UEFI initialization, post tests, and periphial detection.
That's probably 5 seconds on it own.

i said i want to go on linux for 2 years i try to learn, until recently i had the main laptop macbook but now i have switched to linux, i like it more, the ones from Apple are some bastards who take your money on nothing

That is, it lights up quickly I opened the flap of the laptop and it already lit up, after that and when I write high level code, it works faster, in java etc. compile much faster

sudo systemd-analyze tool
[sudo] password for zone:
Unknown operation tool.

  1. Shut down your MacBook - completely
    • Click the Apple logo top left and select Power down
  2. Shutdown the Manjaro laptop - completely
  3. Place them next to each other and press the power button simultanously.

Now that is comparable

no one said tool was an argument.

sudo systemd-analyze blame --no-pager

The initializing of hardware will always take a little time.

If you want your laptop boot faster - in the firmware check if you have a Fastboot option - it is an option which only initializes hardware necessary to start the system - that is it will not probe e.g. USB.

And generic laptop hardware is not comparable to a MacBook - simply because MacBook and macOS are tweaked to optimal performance.

You will never get that kind of integration between generic laptop hardware and Linux.


Fast computer requires slow and long reading of documentation from the user. Take your time!


so its better manjaro, but then what better macbook pro when i put it to sleep, or when compiling programs etc?

how many threads are you using for the compile task on Linux?

4.433s fstrim.service
           697ms man-db.service
           559ms lvm2-monitor.service
           552ms systemd-logind.service
           512ms apparmor.service
           451ms dev-nvme0n1p1.device
           379ms linux-module-cleanup.service
           344ms upower.service
           298ms systemd-udevd.service
           210ms systemd-journald.service
           187ms snapd.service
           160ms var-lib-snapd-snap-core-8213.mount
           147ms var-lib-snapd-snap-code-21.mount
           133ms boot-efi.mount
           127ms udisks2.service
           118ms NetworkManager.service
           109ms ldconfig.service
            98ms systemd-tmpfiles-clean.service
            96ms systemd-journal-flush.service
            77ms systemd-udev-trigger.service
            74ms avahi-daemon.service
            60ms systemd-modules-load.service
            58ms systemd-fsck@dev-disk-by\x2duuid-591F\x2d1488.service
            57ms polkit.service
            56ms user@1000.service
            50ms snapd.apparmor.service
            40ms org.cups.cupsd.service
            32ms var-lib-snapd-snap-code-22.mount
            28ms dev-disk-by\x2duuid-cff2ccd2\x2d5d54\x2d4619\x2d81dc\x2dae16d2ed1249.swap
            27ms systemd-fsck@dev-disk-by\x2duuid-9aec6c82\x2d553a\x2d4cb6\x2d8b19\x2d4f71b0789601.service
            25ms var-lib-snapd-snap-core-8268.mount
            25ms sys-fs-fuse-connections.mount
            24ms systemd-fsck@dev-disk-by\x2duuid-2c211d6b\x2dd4ce\x2d4143\x2d97e8\x2d3cc408d0664a.service
            19ms systemd-backlight@backlight:intel_backlight.service
            14ms systemd-sysusers.service
            14ms systemd-tmpfiles-setup.service
            13ms logrotate.service
            10ms systemd-journal-catalog-update.service
            10ms systemd-tmpfiles-setup-dev.service
             9ms dev-mqueue.mount
             9ms user-runtime-dir@1000.service
             8ms systemd-remount-fs.service
             8ms proc-sys-fs-binfmt_misc.mount
             7ms wpa_supplicant.service
             7ms systemd-rfkill.service
             7ms home.mount
             7ms rtkit-daemon.service
             6ms systemd-sysctl.service
             6ms kmod-static-nodes.service
             6ms systemd-update-utmp.service
             6ms systemd-user-sessions.service
             6ms sys-kernel-debug.mount
             6ms opt.mount
             5ms dev-hugepages.mount
             5ms dev-loop3.device
             4ms systemd-random-seed.service
             4ms systemd-update-done.service
             4ms dev-loop2.device
             4ms dev-loop1.device
             3ms tmp.mount
             2ms sys-kernel-config.mount
           664us snapd.socket

sorry to tell you, i don't know how to tell you

Forum kindly sponsored by