All of a sudden SSH is really lagging/slow.

yawns

@Mar
Thanks for the feedback. I will change my post and remove the =, so others won’t run into the same mistake.

Mar

@strawberry-3.141 My cpu usage (using top) after the pi has booted up stays around 3-5% (using the top command raises this a bit). And memory usage doesnt seem out of control either.

top - 10:36:12 up 43 min,  3 users,  load average: 0.14, 0.12, 0.11
Tasks: 107 total,   1 running, 100 sleeping,   6 stopped,   0 zombie
%Cpu(s):  4.7 us,  1.0 sy,  0.0 ni, 93.9 id,  0.0 wa,  0.0 hi,  0.3 si,  0.0 st
KiB Mem:    445084 total,   340880 used,   104204 free,    26108 buffers
KiB Swap:   102396 total,        0 used,   102396 free.   159376 cached Mem

  PID USER      PR  NI    VIRT    RES    SHR S %CPU %MEM     TIME+ COMMAND                                      
  611 pi        20   0  205560  77592  42308 S  3.3 17.4   1:35.69 midori                                       
 3581 pi        20   0    5232   2596   2160 R  1.6  0.6   0:00.38 top                                          
   60 root      20   0       0      0      0 S  0.3  0.0   0:02.04 kworker/0:2                                  
  594 root      19  -1  154840  47040  21040 S  0.3 10.6   0:16.78 Xorg                                         
 3241 pi        20   0   11940   3440   2768 S  0.3  0.8   0:00.89 sshd                                         
    1 root      20   0    5308   3776   2736 S  0.0  0.8   0:07.32 systemd                                      
    2 root      20   0       0      0      0 S  0.0  0.0   0:00.01 kthreadd                                     
    3 root      20   0       0      0      0 S  0.0  0.0   0:01.17 ksoftirqd/0

Im using the following modules.

profileswitcher, buttons, clock, calendar, compliments, current weather, weather forecast, wunderlist, newsfeed, calendar monthly, tube status, and system stats.

Snille

@strawberry-3-141 Hmm… It does not seam to be any module doing it… I’m thinking it’s a “core-dump”, I noticed when restarting that it took a long time before it actually restarted. I’m guessing something did not close down properly, then the memory (or something) is dumped down to a file… Now it’s not happening any longer… Reboots normally. Only thing is that I lost my pm2 autostart of the mirror for some reason (had to do a pm2 startup and run the “setup” command sudo env PATH=$PATH:/usr/bin /usr/lib/node_modules/pm2/bin/pm2 startup systemd -u pi --hp /home/pi again… And now it starts normally again… No core file after reboots, all modules back again… Darn! :)

strawberry 3.141

@Mar does the ssh speedup when you shut down the mirror?

Mar

@strawberry-3.141 Oh wow! Ran a pm2 stop mm and the ssh went back to exactly how it used to be. No lag at all and can use nano on the config file with zero lag (could even mouse wheel scroll perfectly).

Then starting MM back up (pm2 start mm) it seems to maintain the quick ssh speed. Upon a full reboot though it seems to get back to being slightly slower.

Snille

Just got myself a “core”-file again in the MM root. :) I’m now sure it’s because Electron is crashing. So, it’s probably a memory dump. Still don’t really know why Electron is crashing. It’s not crashing all the time. Just sometimes. But then, I do have lot’s of modules going… :)