0

I am using Ubuntu 14.04 on my computer that acts as a server. Short pc spec list (lshw): http://pastebin.com/7ud6rpxX

The average number of procs is 500 (I have got a little widget that I forgot the name of on my desktop)

The server is running a GitLab server on it with a runner connected to it, but it isn't doing anything at the time of being slow. There is not really any connection to the things the server does on GitLab and the performance of the system.

The one moment it's fast, the other it's slow. Can't find out why, also the booting is very very slow (the terminal kind of bootdetails list is progressing very slow and takes it's time)

Should I disable the visual effects?

Thanks,

Tim

EDIT: I haven't found anything that uses my cpu above 2,5% and my memory above 8%. Could it be the GPU giving up?

EDIT: Here is the second bootchart image:

HIGH RES

EDIT: This is the bootchart with the ureadahead pack file removed:

HIGH RES with pack file removed

Bootchart of 16/04/25

tim687
  • 131
  • 1
  • 8
  • Image quality is too low. Something on top of booting is taking too long (maybe ureadahead - can't see) – EdiD Apr 26 '16 at 08:30
  • @EdiD Sorry, didn't see that. Here is the file itself: http://www.mediafire.com/view/s4ac39na9ob3sow/Bootchart.png The first big thing is indeed unreadahead – tim687 Apr 26 '16 at 10:51
  • `ureadahead` is slowing boot try to purge cache by removing any pack files in the `/var/lib/ureadahead` directory. – EdiD Apr 26 '16 at 11:40
  • @EdiD I think I might have the fix: clean your system from time to time. I think my GPU was thermal throttling that much that the whole system became slow. – tim687 Apr 26 '16 at 17:54
  • Cleaning is definitely good but GPU has nothing to 50s `ureadahead` delay on boot – EdiD Apr 26 '16 at 20:16
  • @EdiD That did not fixed it unfortunately. I'll check the bootchart since I did remove the pack file. – tim687 Apr 27 '16 at 07:25
  • @EdiD Please check my updated question. – tim687 Apr 27 '16 at 09:55
  • First boot after deleting pack files will rebuild ureadahead cache so it could be slower than normal. If next boot are the same slow try to disable ureadahead : `sudo tee /etc/init/ureadahead.override <<< manual` – EdiD Apr 27 '16 at 13:32
  • @EdiD I was backing up my system so I couldn't reboot it. But bootchart showed a decrease of ureadahead 'waiting time' of around 1 minute. So it seems that this fix is working for now. Does disabling bootchart improve the booting time? Or can I just leave it enabled? – tim687 May 02 '16 at 10:36
  • If everything is ok you may consider disabling – EdiD May 02 '16 at 16:55

1 Answers1

0

At first you have to know what is causing this slows. You can monitor if your cpu is not excessive loaded: 

watch "ps aux --sort -pcpu | head -11"

This will monitor every default 2s top 10 consuming cpu processes. You can send it to log file for further investigation with a little tee help:

watch "ps aux --sort -pcpu | head -11 | tee -a logfile"

In the same way you can monitor memory usage 

watch "ps aux --sort -rss | head -11"

For slow booting problems. You can install bootchart

sudo apt-get install bootchart

reboot your system and analyse chart which should be placed in /var/log/bootchart. It should tell you what causes slow boot. After all you can disable bootchart service with:

sudo tee -a /etc/init/bootchart.override <<< manual

You can also use tools like top for process monitoring and iotop for I/O operations and check logs /var/log/syslog,/var/log/kern.log, /var/log/boot.log for "suspicious" entries

EdiD
  • 4,327
  • 3
  • 23
  • 40
  • Thanks for this, I am definitely going to try this! I will post the results in my question above. – tim687 Apr 21 '16 at 06:14
  • Sorry for answering this late, I am having big time issues with my GitLab instance, which are not yet resolved. But I have attached the bootchart picture in the question. If you want me to send the tgz file, just pm me. Thanks! – tim687 Apr 25 '16 at 19:25
  • I am sorry to say to, but the problem is still occuring, I'll try to boot to Windows on that machine to check if is an Ubuntu related issue. I am hoping it is, but on the other side I am not. – tim687 May 10 '16 at 09:19