You are not logged in.

#1 2017-07-01 20:49:54

emek
Member
Registered: 2017-02-28
Posts: 49

[SOLVED] Improve startup time

Hi there, I recently noticed that it takes a lot of time to boot my netbook.

When I installed Bunsen, years ago, the boot time it was pretty fast, let say like 40 seconds. Now, it takes like 2 minutes.
I know that this is a dumb thing, but I start to think that the whole system is running in a worst state, for example Chromium take like 60 second to start and even the terminal take like 10 seconds.

I have to say that my netbook is not a fast machine as you can imagine: 2 GB of RAM, Intel(R) Atom(TM) CPU N2600   @ 1.60GHz. But i remember that it wasn't too bad few months ago.

Can you tell me what I can check to realize why is this happening?

pd: I don't speak very well English, so if a write something bad, my apologizes.

Last edited by Head_on_a_Stick (2017-08-06 19:30:01)

Offline

#2 2017-07-01 20:58:03

Head_on_a_Stick
Member
From: London
Registered: 2015-09-29
Posts: 9,093
Website

Re: [SOLVED] Improve startup time

Can we please see the output of these commands:

systemd-analyze
systemd-analyze blame --no-pager
systemd-analyze critical-chain --no-pager
df -h
free -h

Thanks!

Last edited by Head_on_a_Stick (2017-07-01 21:01:09)

Offline

#3 2017-07-01 21:17:34

Martin
Member
From: Stockholm, Sweden
Registered: 2015-10-01
Posts: 801
Website

Re: [SOLVED] Improve startup time

Cool commands :-)

/Martin


"Problems worthy of attack
prove their worth by hitting back."
Piet Hein

Offline

#4 2017-07-01 21:22:55

emek
Member
Registered: 2017-02-28
Posts: 49

Re: [SOLVED] Improve startup time

Head_on_a_Stick wrote:

Can we please see the output of these commands:

systemd-analyze
systemd-analyze blame --no-pager
systemd-analyze critical-chain --no-pager
df -h
free -h

Thanks!

Thanks to you. Here are the output

systemd-analyze

Startup finished in 5.877s (kernel) + 26.846s (userspace) = 32.723s
23s

Aparently I'm very bad on taking time. According to this,the boot process take just 33s, but i feel like more time. The output say "26.846s (userspace)" this mean that the boot time is getting high because my files?

systemd-analyze blame --no-pager

         17.930s nmbd.service
         17.363s samba-ad-dc.service
          9.083s NetworkManager.service
          6.790s ModemManager.service
          5.538s alsa-restore.service
          4.732s loadcpufreq.service
          3.870s systemd-logind.service
          3.804s lm-sensors.service
          3.785s rc-local.service
          3.781s ntp.service
          3.780s irqbalance.service
          3.779s gdomap.service
          3.778s exim4.service
          3.774s hddtemp.service
          3.420s networking.service
          2.469s systemd-tmpfiles-setup.service
          2.222s lightdm.service
          2.007s polkitd.service
          1.779s kbd.service
          1.644s rsyslog.service
          1.173s smbd.service
          1.140s keyboard-setup.service
           939ms console-setup.service
           730ms systemd-journal-flush.service
           698ms systemd-rfkill@rfkill0.service
           661ms dev-mqueue.mount
           537ms sys-kernel-debug.mount
           534ms dev-hugepages.mount
           526ms hdparm.service
           453ms systemd-modules-load.service
           430ms wpa_supplicant.service
           418ms user@108.service
           415ms kmod-static-nodes.service
           355ms systemd-tmpfiles-setup-dev.service
           338ms systemd-setup-dgram-qlen.service
           327ms systemd-udev-trigger.service
           263ms systemd-random-seed.service
           219ms systemd-remount-fs.service
           199ms cpufrequtils.service
           192ms systemd-update-utmp.service
           191ms udisks2.service
           185ms systemd-backlight@backlight:acpi_video0.service
           129ms systemd-user-sessions.service
           123ms systemd-tmpfiles-clean.service
            93ms systemd-backlight@backlight:psb-bl.service
            77ms systemd-rfkill@rfkill1.service
            76ms upower.service
            69ms sys-fs-fuse-connections.mount
            64ms dev-disk-by\x2duuid-b346da01\x2d20d1\x2d4332\x2db8b4\x2d55ff22e45622.swap
            54ms systemd-sysctl.service
            45ms user@1000.service
            36ms udev-finish.service
            19ms systemd-udevd.service
            18ms systemd-update-utmp-runlevel.service

systemd-analyze critical-chain --no-pager

The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.

graphical.target @26.802s
└─multi-user.target @26.801s
  └─smbd.service @25.627s +1.173s
    └─nmbd.service @7.675s +17.930s
      └─basic.target @7.627s
        └─timers.target @7.613s
          └─systemd-tmpfiles-clean.timer @7.613s
            └─sysinit.target @7.612s
              └─swap.target @7.612s
                └─dev-disk-by\x2duuid-b346da01\x2d20d1\x2d4332\x2db8b4\x2d55ff22e45622.swap @7.539s +64ms
                  └─dev-disk-by\x2duuid-b346da01\x2d20d1\x2d4332\x2db8b4\x2d55ff22e45622.device @7.525s

df -h

Filesystem      Size  Used Avail Use% Mounted on
udev             10M     0   10M   0% /dev
tmpfs           402M  1.1M  401M   1% /run
/dev/sda3        46G   30G   14G  69% /
tmpfs          1005M   33M  973M   4% /dev/shm
tmpfs           5.0M  4.0K  5.0M   1% /run/lock
tmpfs          1005M     0 1005M   0% /sys/fs/cgroup
tmpfs           201M  4.0K  201M   1% /run/user/108
tmpfs           201M  8.0K  201M   1% /run/user/1000

free -h

             total       used       free     shared    buffers     cached
Mem:          2.0G       1.8G       137M        37M        88M       1.1G
-/+ buffers/cache:       657M       1.3G
Swap:         3.4G       152K       3.4G

Last edited by emek (2017-07-01 21:27:27)

Offline

#5 2017-07-02 13:55:11

Head_on_a_Stick
Member
From: London
Registered: 2015-09-29
Posts: 9,093
Website

Re: [SOLVED] Improve startup time

^ Well that all looks pretty normal.

When you experience the sluggish response, what processes are listed first in the Task Manager (`htop`)?

You can also run this command to analyse which systemd unit files are using up your resources:

systemd-cgtop

Additionally, iotop is useful for spotting I/O problems.

If none of those make any sense to you, wait until your desktop is running slowly then run this command and post the output here:

ps aux

Offline

#6 2017-07-02 14:32:51

DeepDayze
Like sands through an hourglass...
From: In Linux Land
Registered: 2017-05-28
Posts: 1,901

Re: [SOLVED] Improve startup time

@emek, looks like also your memory is getting close to exhausted as well considering your system has started to use swap space according to that free command output you posted. Maybe add more RAM if possible?


Real Men Use Linux

Offline

#7 2017-07-02 14:34:56

Head_on_a_Stick
Member
From: London
Registered: 2015-09-29
Posts: 9,093
Website

Re: [SOLVED] Improve startup time

DeepDayze wrote:

@emek, looks like also your memory is getting close to exhausted

Take a look at the "used" & "free" totals on the second line, these show the amounts before caching is accounted for.

See http://www.linuxatemyram.com/ for more on this.

EDIT: that site is a little dated now because the output of the `free` command was changed recently to make the situation more clear.

Last edited by Head_on_a_Stick (2017-07-02 14:37:10)

Offline

#8 2017-07-02 14:48:47

DeepDayze
Like sands through an hourglass...
From: In Linux Land
Registered: 2017-05-28
Posts: 1,901

Re: [SOLVED] Improve startup time

Head_on_a_Stick wrote:
DeepDayze wrote:

@emek, looks like also your memory is getting close to exhausted

Take a look at the "used" & "free" totals on the second line, these show the amounts before caching is accounted for.

See http://www.linuxatemyram.com/ for more on this.

EDIT: that site is a little dated now because the output of the `free` command was changed recently to make the situation more clear.

OK my bad, so system caching is using a little swap then?


Real Men Use Linux

Offline

#9 2017-07-02 14:54:18

Head_on_a_Stick
Member
From: London
Registered: 2015-09-29
Posts: 9,093
Website

Re: [SOLVED] Improve startup time

^ Yes, it looks like the OP's system is caching correctly and not using (much) swap, as it should be.

2GiB should be more than enough for BunsenLabs unless the user likes VMs (containers ftw!) or compiles large programs from source (unlikely with an Atom processor).

Offline

#10 2017-07-02 21:20:48

emek
Member
Registered: 2017-02-28
Posts: 49

Re: [SOLVED] Improve startup time

Only once I compile a program (firefox) to see if the performance is improve. When I do that, the whole process take like 12 hours, so I never did it again.

I'll wait until my desktop running slowly and come back here to post the output of ps aux.

Thanks you smile

Offline

#11 2017-07-06 23:24:40

emek
Member
Registered: 2017-02-28
Posts: 49

Re: [SOLVED] Improve startup time

Hi again. Just like say @Head_on_a_Stick, i post the output of ps aux when i have a poor performance

USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
root         1  0.5  0.2   5508  4248 ?        Ss   19:07   0:02 /sbin/init
root         2  0.0  0.0      0     0 ?        S    19:07   0:00 [kthreadd]
root         3  0.0  0.0      0     0 ?        S    19:07   0:00 [ksoftirqd/0]
root         5  0.0  0.0      0     0 ?        S<   19:07   0:00 [kworker/0:0H]
root         7  0.2  0.0      0     0 ?        S    19:07   0:01 [rcu_sched]
root         8  0.0  0.0      0     0 ?        S    19:07   0:00 [rcu_bh]
root         9  0.0  0.0      0     0 ?        S    19:07   0:00 [migration/0]
root        10  0.0  0.0      0     0 ?        S    19:07   0:00 [watchdog/0]
root        11  0.0  0.0      0     0 ?        S    19:07   0:00 [cpuhp/0]
root        12  0.0  0.0      0     0 ?        S    19:07   0:00 [cpuhp/1]
root        13  0.0  0.0      0     0 ?        S    19:07   0:00 [watchdog/1]
root        14  0.0  0.0      0     0 ?        S    19:07   0:00 [migration/1]
root        15  0.0  0.0      0     0 ?        S    19:07   0:00 [ksoftirqd/1]
root        17  0.0  0.0      0     0 ?        S<   19:07   0:00 [kworker/1:0H]
root        18  0.0  0.0      0     0 ?        S    19:07   0:00 [cpuhp/2]
root        19  0.0  0.0      0     0 ?        S    19:07   0:00 [watchdog/2]
root        20  0.0  0.0      0     0 ?        S    19:07   0:00 [migration/2]
root        21  0.0  0.0      0     0 ?        S    19:07   0:00 [ksoftirqd/2]
root        23  0.0  0.0      0     0 ?        S<   19:07   0:00 [kworker/2:0H]
root        24  0.0  0.0      0     0 ?        S    19:07   0:00 [cpuhp/3]
root        25  0.0  0.0      0     0 ?        S    19:07   0:00 [watchdog/3]
root        26  0.0  0.0      0     0 ?        S    19:07   0:00 [migration/3]
root        27  0.0  0.0      0     0 ?        S    19:07   0:00 [ksoftirqd/3]
root        29  0.0  0.0      0     0 ?        S<   19:07   0:00 [kworker/3:0H]
root        30  0.0  0.0      0     0 ?        S    19:07   0:00 [kdevtmpfs]
root        31  0.0  0.0      0     0 ?        S<   19:07   0:00 [netns]
root        32  0.0  0.0      0     0 ?        S    19:07   0:00 [khungtaskd]
root        33  0.0  0.0      0     0 ?        S    19:07   0:00 [oom_reaper]
root        34  0.0  0.0      0     0 ?        S<   19:07   0:00 [writeback]
root        35  0.0  0.0      0     0 ?        S    19:07   0:00 [kcompactd0]
root        36  0.0  0.0      0     0 ?        SN   19:07   0:00 [ksmd]
root        37  0.0  0.0      0     0 ?        SN   19:07   0:00 [khugepaged]
root        38  0.0  0.0      0     0 ?        S    19:07   0:00 [kworker/1:1]
root        39  0.0  0.0      0     0 ?        S<   19:07   0:00 [crypto]
root        40  0.0  0.0      0     0 ?        S<   19:07   0:00 [kintegrityd]
root        41  0.0  0.0      0     0 ?        S<   19:07   0:00 [bioset]
root        42  0.0  0.0      0     0 ?        S<   19:07   0:00 [kblockd]
root        43  0.0  0.0      0     0 ?        S    19:07   0:00 [kworker/0:1]
root        44  0.0  0.0      0     0 ?        S<   19:07   0:00 [devfreq_wq]
root        45  0.0  0.0      0     0 ?        S<   19:07   0:00 [watchdogd]
root        46  0.0  0.0      0     0 ?        S    19:07   0:00 [kworker/3:1]
root        47  0.0  0.0      0     0 ?        S    19:07   0:00 [kswapd0]
root        48  0.0  0.0      0     0 ?        S<   19:07   0:00 [vmstat]
root        61  0.0  0.0      0     0 ?        S<   19:07   0:00 [kthrotld]
root        62  0.1  0.0      0     0 ?        S    19:07   0:00 [kworker/2:1]
root        63  0.0  0.0      0     0 ?        S<   19:07   0:00 [ipv6_addrconf]
root        64  0.0  0.0      0     0 ?        S    19:07   0:00 [kworker/2:2]
root        65  0.1  0.0      0     0 ?        S    19:07   0:00 [kworker/u8:1]
root        70  0.0  0.0      0     0 ?        S<   19:07   0:00 [deferwq]
root       109  0.0  0.0      0     0 ?        S<   19:07   0:00 [acpi_thermal_pm]
root       110  0.0  0.0      0     0 ?        S<   19:07   0:00 [ata_sff]
root       111  0.0  0.0      0     0 ?        S<   19:07   0:00 [kpsmoused]
root       112  0.1  0.0      0     0 ?        S    19:07   0:00 [kworker/1:2]
root       113  0.0  0.0      0     0 ?        S    19:07   0:00 [scsi_eh_0]
root       114  0.0  0.0      0     0 ?        S<   19:07   0:00 [scsi_tmf_0]
root       115  0.0  0.0      0     0 ?        S    19:07   0:00 [scsi_eh_1]
root       116  0.0  0.0      0     0 ?        S<   19:07   0:00 [scsi_tmf_1]
root       117  0.0  0.0      0     0 ?        S    19:07   0:00 [scsi_eh_2]
root       118  0.0  0.0      0     0 ?        S<   19:07   0:00 [scsi_tmf_2]
root       119  0.0  0.0      0     0 ?        S    19:07   0:00 [scsi_eh_3]
root       120  0.0  0.0      0     0 ?        S<   19:07   0:00 [scsi_tmf_3]
root       121  0.1  0.0      0     0 ?        S    19:07   0:00 [kworker/u8:2]
root       125  0.0  0.0      0     0 ?        S    19:07   0:00 [kworker/3:2]
root       126  0.0  0.0      0     0 ?        S<   19:07   0:00 [bioset]
root       129  0.0  0.0      0     0 ?        S<   19:07   0:00 [kworker/2:1H]
root       130  0.0  0.0      0     0 ?        S<   19:07   0:00 [kworker/3:1H]
root       132  0.0  0.0      0     0 ?        S    19:07   0:00 [scsi_eh_4]
root       133  0.0  0.0      0     0 ?        S<   19:07   0:00 [scsi_tmf_4]
root       134  0.0  0.0      0     0 ?        S    19:07   0:00 [usb-storage]
root       135  0.0  0.0      0     0 ?        S<   19:07   0:00 [kworker/0:1H]
root       136  0.0  0.0      0     0 ?        S<   19:07   0:00 [kworker/1:1H]
root       142  0.0  0.0      0     0 ?        S<   19:07   0:00 [bioset]
root       147  0.0  0.0      0     0 ?        S<   19:07   0:00 [bioset]
root       166  0.0  0.0      0     0 ?        S    19:07   0:00 [jbd2/sda3-8]
root       167  0.0  0.0      0     0 ?        S<   19:07   0:00 [ext4-rsv-conver]
root       198  0.1  0.0      0     0 ?        S    19:08   0:00 [kworker/0:2]
root       199  0.0  0.0      0     0 ?        S    19:08   0:00 [kauditd]
root       203  0.1  0.3  20588  7420 ?        Ss   19:08   0:00 /lib/systemd/systemd-journald
root       218  0.1  0.1  13092  3720 ?        Ss   19:08   0:00 /lib/systemd/systemd-udevd
root       313  0.0  0.0      0     0 ?        S<   19:08   0:00 [cfg80211]
root       501  0.5  0.6  68720 13532 ?        Ssl  19:08   0:02 /usr/sbin/NetworkManager --no-daemon
root       503  0.0  0.1   4924  3468 ?        Ss   19:08   0:00 /usr/sbin/smartd -n
root       505  0.0  0.1   5024  2752 ?        Ss   19:08   0:00 /usr/sbin/cron -f
root       506  0.0  0.3  41064  7408 ?        Ssl  19:08   0:00 /usr/sbin/ModemManager
root       508  0.0  0.1   3776  2812 ?        Ss   19:08   0:00 /lib/systemd/systemd-logind
message+   524  0.2  0.1   5636  3604 ?        Ss   19:08   0:01 /usr/bin/dbus-daemon --system --address=systemd: --nofork --no
root       544  0.0  0.1  32024  3244 ?        Ssl  19:08   0:00 /usr/sbin/rsyslogd -n
root       552  0.0  0.0   4188  1908 tty1     Ss+  19:08   0:00 /sbin/agetty --noclear tty1 linux
root       556  0.0  0.3  40792  7568 ?        SLsl 19:08   0:00 /usr/sbin/lightdm
root       557  0.0  0.1   4328  2088 ?        Ss   19:08   0:00 /usr/sbin/irqbalance --pid=/var/run/irqbalance.pid
ntp        558  0.0  0.1   5744  4052 ?        Ss   19:08   0:00 /usr/sbin/ntpd -p /var/run/ntpd.pid -g -u 105:110
root       576  0.0  0.4  43184  8676 ?        Ssl  19:08   0:00 /usr/lib/policykit-1/polkitd --no-debug
root       600  7.7  2.5 146696 52232 tty7     Ssl+ 19:08   0:39 /usr/bin/X :0 -seat seat0 -auth /var/run/lightdm/root/:0 -noli
root       640  0.0  0.2   7768  5836 ?        Ss   19:08   0:00 /sbin/wpa_supplicant -u -s -O /run/wpa_supplicant
root       689  0.0  0.3   9260  7844 ?        S    19:08   0:00 /sbin/dhclient -d -q -sf /usr/lib/NetworkManager/nm-dhcp-helpe
lightdm    690  0.0  0.1   5008  3620 ?        Ss   19:08   0:00 /lib/systemd/systemd --user
lightdm    691  0.0  0.0   6392  1332 ?        S    19:08   0:00 (sd-pam)  
lightdm    700  0.0  0.0   3988  1980 ?        S    19:08   0:00 /usr/bin/dbus-launch --autolaunch 076b550ddd9f43acadc737935d92
lightdm    701  0.0  0.1   5256  2344 ?        Ss   19:08   0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --
lightdm    704  0.0  0.3  50188  7160 ?        Sl   19:08   0:00 /usr/lib/at-spi2-core/at-spi-bus-launcher
lightdm    714  0.0  0.1   5256  3272 ?        S    19:08   0:00 /usr/bin/dbus-daemon --config-file=/etc/at-spi2/accessibility.
lightdm    717  0.0  0.2  18268  4788 ?        Sl   19:08   0:00 /usr/lib/at-spi2-core/at-spi2-registryd --use-gnome-session
root       755  0.0  0.2  21348  4732 ?        Ss   19:08   0:00 /usr/sbin/nmbd -D
root       767  0.0  0.6  34976 13328 ?        Ss   19:08   0:00 /usr/sbin/smbd -D
root       771  0.0  0.1  34976  3740 ?        S    19:08   0:00 /usr/sbin/smbd -D
root       776  0.0  0.3  32368  8072 ?        Sl   19:09   0:00 lightdm --session-child 13 22
emek   782  0.0  0.1   5000  3680 ?        Ss   19:09   0:00 /lib/systemd/systemd --user
emek   783  0.0  0.0   6392  1332 ?        S    19:09   0:00 (sd-pam)  
emek   787  0.0  0.3  52552  7984 ?        Sl   19:09   0:00 /usr/bin/gnome-keyring-daemon --daemonize --login
emek   789  0.1  0.6  21712 13200 ?        Ss   19:09   0:00 /usr/bin/openbox --startup /usr/lib/i386-linux-gnu/openbox-aut
emek   816  0.0  0.0   3988  1984 ?        S    19:09   0:00 dbus-launch --autolaunch=076b550ddd9f43acadc737935d92402b --bi
emek   817  0.0  0.0   5256   284 ?        Ss   19:09   0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --
emek   818  0.0  0.0   4440   216 ?        Ss   19:09   0:00 /usr/bin/ssh-agent /usr/bin/dbus-launch --exit-with-session x-
emek   821  0.0  0.0   3988  1984 ?        S    19:09   0:00 /usr/bin/dbus-launch --exit-with-session x-session-manager
emek   822  0.0  0.1   5508  2604 ?        Ss   19:09   0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --
emek   839  0.2  1.2  47752 26020 ?        Sl   19:09   0:01 /usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1
emek   847  0.7  1.2  61928 25440 ?        Sl   19:09   0:03 thunar --daemon
emek   853  0.0  0.3  50200  7492 ?        Sl   19:09   0:00 /usr/lib/at-spi2-core/at-spi-bus-launcher
emek   859  0.0  0.1   5256  3200 ?        S    19:09   0:00 /usr/bin/dbus-daemon --config-file=/etc/at-spi2/accessibility.
emek   862  0.0  0.2  18268  4644 ?        Sl   19:09   0:00 /usr/lib/at-spi2-core/at-spi2-registryd --use-gnome-session
emek   874  0.0  0.1   7180  4048 ?        S    19:09   0:00 /usr/lib/i386-linux-gnu/xfce4/xfconf/xfconfd
emek   875  0.2  0.9  39468 19356 ?        Ssl  19:09   0:01 xfce4-power-manager
emek   880  1.8  0.6  93536 12928 ?        Ss   19:09   0:08 compton -b --vsync opengl
emek   884  0.1  0.9  39164 20032 ?        Sl   19:09   0:00 /usr/lib/i386-linux-gnu/xfce4/notifyd/xfce4-notifyd
emek   888  0.3  0.3 100336  8112 ?        Sl   19:09   0:01 /usr/bin/pulseaudio --start --log-target=syslog
root       889  0.0  0.3  41708  7948 ?        Ssl  19:09   0:00 /usr/lib/upower/upowerd
emek   905  0.0  0.5  16264 11068 ?        S    19:09   0:00 tint2 -c /home/emek/.config/tint2/tint2rc
emek   920  0.0  0.7 112760 16360 ?        Sl   19:09   0:00 volumeicon
emek   923  0.2  1.3  78804 27096 ?        Sl   19:09   0:01 nm-applet
emek   925  0.0  0.7  40732 16312 ?        Sl   19:09   0:00 light-locker
emek   930  0.0  0.2  31284  6128 ?        Sl   19:09   0:00 /usr/lib/gvfs/gvfsd
emek   934  0.0  0.2  48976  5736 ?        Sl   19:09   0:00 /usr/lib/gvfs/gvfsd-fuse /run/user/1000/gvfs -f -o big_writes
emek   945  0.0  0.2   9288  4856 ?        S    19:09   0:00 /usr/lib/i386-linux-gnu/gconf/gconfd-2
emek   950 22.0  7.2 724840 149464 ?       Sl   19:09   1:30 /usr/lib/chromium/chromium --incognito
emek   955  0.0  0.0   2288   688 ?        S    19:09   0:00 /usr/lib/chromium/chrome-sandbox /usr/lib/chromium/chromium --
emek   956  0.0  1.3 206172 27160 ?        S    19:09   0:00 /usr/lib/chromium/chromium --type=zygote
emek   958  0.0  0.9 206172 18744 ?        S    19:09   0:00 /usr/lib/chromium/chromium --type=zygote
emek  1007  0.4  3.1 346636 65668 ?        Sl   19:10   0:01 /usr/lib/chromium/chromium --type=renderer --field-trial-handl
emek  1012  0.9  4.1 448228 86092 ?        Sl   19:10   0:03 /usr/lib/chromium/chromium --type=renderer --field-trial-handl
emek  1017  3.9  4.0 404656 83136 ?        Sl   19:10   0:15 /usr/lib/chromium/chromium --type=renderer --field-trial-handl
emek  1025  2.5  4.6 474736 94924 ?        Sl   19:10   0:10 /usr/lib/chromium/chromium --type=renderer --field-trial-handl
emek  1073  0.1  2.6 311696 53740 ?        Sl   19:10   0:00 /usr/lib/chromium/chromium --type=gpu-process --field-trial-ha
emek  1126 32.7 15.3 693480 316188 ?       Sl   19:10   1:53 /usr/lib/chromium/chromium --type=renderer --field-trial-handl
emek  1209  1.7  2.3 148432 48876 ?        Sl   19:12   0:04 evince /home/emek/Downloads/Lehrer, Schauble, Petrosino (2
emek  1215  0.0  0.0  15756  2036 ?        Sl   19:12   0:00 /usr/lib/evince/evinced
emek  1230  0.0  0.2  21236  5788 ?        Sl   19:12   0:00 /usr/lib/gvfs/gvfsd-metadata
root      1238  0.0  0.0      0     0 ?        S    19:13   0:00 [kworker/1:0]
root      1246  0.0  0.0      0     0 ?        S    19:13   0:00 [kworker/0:0]
root      1248  0.1  0.0      0     0 ?        S    19:13   0:00 [kworker/3:0]
root      1250  0.0  0.0      0     0 ?        S    19:13   0:00 [kworker/u8:0]
root      1251  0.0  0.0      0     0 ?        S    19:13   0:00 [kworker/2:0]
emek  1282 16.0  5.5 447992 115016 ?       Sl   19:14   0:22 /usr/lib/chromium/chromium --type=renderer --field-trial-handl
emek  1309  0.1  0.4  61560  9040 ?        Sl   19:14   0:00 /usr/lib/gvfs/gvfs-udisks2-volume-monitor
root      1311  0.4  0.4  60000  8564 ?        Ssl  19:14   0:00 /usr/lib/udisks2/udisksd --no-debug
emek  1320  0.0  0.2  30488  5736 ?        Sl   19:14   0:00 /usr/lib/gvfs/gvfs-goa-volume-monitor
emek  1324  0.0  0.3  43016  6880 ?        Sl   19:14   0:00 /usr/lib/gvfs/gvfs-afc-volume-monitor
emek  1329  0.0  0.2  30212  5408 ?        Sl   19:14   0:00 /usr/lib/gvfs/gvfs-mtp-volume-monitor
emek  1333  0.0  0.2  31072  5916 ?        Sl   19:14   0:00 /usr/lib/gvfs/gvfs-gphoto2-volume-monitor
emek  1337  0.0  0.3  51492  7652 ?        Sl   19:14   0:00 /usr/lib/gvfs/gvfsd-trash --spawner :1.14 /org/gtk/gvfs/exec_s
root      1349  4.9  0.1   5168  2596 ?        Ss   19:14   0:05 /sbin/mount.ntfs /dev/sda2 /media/emek/84AAC9E2AAC9D13A -o
emek  1443 14.3  1.8  69044 38244 ?        Rl   19:16   0:01 /usr/bin/python /usr/bin/x-terminal-emulator -b
emek  1449  0.1  0.0   2428  1596 ?        S    19:16   0:00 gnome-pty-helper
emek  1450  1.7  0.2   6840  4780 pts/1    Ss   19:16   0:00 /bin/bash
emek  1458  0.0  0.1   4784  2480 pts/1    R+   19:16   0:00 ps aux

Offline

#12 2017-07-07 06:40:20

Head_on_a_Stick
Member
From: London
Registered: 2015-09-29
Posts: 9,093
Website

Re: [SOLVED] Improve startup time

^ Well that all looks fine, nothing is running up the processor so it must be I/O related.

Let's try this (again, when the system is sluggish):

sudo apt install sysstat
sudo iostat

Please post the full output of the second command.

EDIT: package name corrected, thanks John!

Last edited by Head_on_a_Stick (2017-07-07 21:08:49)

Offline

#13 2017-07-07 09:16:21

johnraff
nullglob
From: Nagoya, Japan
Registered: 2015-09-09
Posts: 12,666
Website

Re: [SOLVED] Improve startup time

^sysstat (But thanks for the hint anyway!)


...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )

Introduction to the Bunsenlabs Boron Desktop

Offline

#14 2017-07-08 17:10:28

emek
Member
Registered: 2017-02-28
Posts: 49

Re: [SOLVED] Improve startup time

Head_on_a_Stick wrote:

^ Well that all looks fine, nothing is running up the processor so it must be I/O related.

Let's try this (again, when the system is sluggish):

sudo apt install sysstat
sudo iostat

Please post the full output of the second command.

EDIT: package name corrected, thanks John!

Here is the full output of sysstat big_smile

Linux 4.6.0-0.bpo.1-686 (bunsen) 	07/08/2017 	_i686_	(4 CPU)

avg-cpu:  %user   %nice %system %iowait  %steal   %idle
           7.81    0.13    3.15    6.99    0.00   81.93

Device:            tps    kB_read/s    kB_wrtn/s    kB_read    kB_wrtn
sda              47.62       984.88       184.54     442380      82888

Last edited by emek (2017-07-08 17:11:52)

Offline

#15 2017-07-09 08:02:39

johnraff
nullglob
From: Nagoya, Japan
Registered: 2015-09-09
Posts: 12,666
Website

Re: [SOLVED] Improve startup time

BTW on my (Jessie) system there's no difference between the output of 'sudo iostat' and plain 'iostat'.


...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )

Introduction to the Bunsenlabs Boron Desktop

Offline

#16 2017-07-09 10:28:29

Head_on_a_Stick
Member
From: London
Registered: 2015-09-29
Posts: 9,093
Website

Re: [SOLVED] Improve startup time

That output also looks completely normal apart from...

emek wrote:
Linux 4.6.0-0.bpo.1-686

Why are you running such an old kernel?

That particular version has several known vulnerabilities, including the recent high-profile "Stack Clash" exploit, and should be upgraded as soon as possible.

The best kernel to use is the 3.16 version that comes with BunsenLabs, this will always be updated very quickly in the event of any potential exploits being discovered.

Offline

#17 2017-07-11 16:50:48

emek
Member
Registered: 2017-02-28
Posts: 49

Re: [SOLVED] Improve startup time

Head_on_a_Stick wrote:

That output also looks completely normal apart from...

emek wrote:
Linux 4.6.0-0.bpo.1-686

Why are you running such an old kernel?

That particular version has several known vulnerabilities, including the recent high-profile "Stack Clash" exploit, and should be upgraded as soon as possible.

The best kernel to use is the 3.16 version that comes with BunsenLabs, this will always be updated very quickly in the event of any potential exploits being discovered.

Ohh, I use sudo apt-get update and dist-upgrade to keep my system update. According to that commands, I have my system update.

edit:
I just remember I follow this topic of @Head_on_a_Stick months ago, and I install that kernel because it say "Linux for older PCs"
https://forums.bunsenlabs.org/viewtopic.php?id=1257

I install this one now:
linux-image-3.16.0-4-586

Last edited by emek (2017-07-11 17:46:17)

Offline

#18 2017-07-11 19:31:00

Head_on_a_Stick
Member
From: London
Registered: 2015-09-29
Posts: 9,093
Website

Re: [SOLVED] Improve startup time

emek wrote:

I install this one now:
linux-image-3.16.0-4-586

Yes, good, that is the one that will probably work best.

Have you had the same problems with that kernel?

Offline

#19 2017-07-11 23:24:43

emek
Member
Registered: 2017-02-28
Posts: 49

Re: [SOLVED] Improve startup time

So far, so good!

Could be possible that the performance was worst because of the kernel?

One last thing, now I have the kernel manually installed, is there a way to autoupdate it?
If I'm not wrong, when I apply sudo apt update and apt dist-upgrade , the kernel will not be update, right?

Offline

#20 2017-07-12 01:34:59

DeepDayze
Like sands through an hourglass...
From: In Linux Land
Registered: 2017-05-28
Posts: 1,901

Re: [SOLVED] Improve startup time

emek wrote:

So far, so good!

Could be possible that the performance was worst because of the kernel?

One last thing, now I have the kernel manually installed, is there a way to autoupdate it?
If I'm not wrong, when I apply sudo apt update and apt dist-upgrade , the kernel will not be update, right?

The kernel is normally not updated in an upgrade unless you have installed the kernel metapackages as these will then pull in the new kernel for you when the metapackage is updated.


Real Men Use Linux

Offline

Board footer

Powered by FluxBB