View previous topic :: View next topic |
Author |
Message |
jesnow l33t
Joined: 26 Apr 2006 Posts: 856
|
Posted: Tue Feb 27, 2018 3:10 am Post subject: Unexplained performance loss [SOLVED I THINK!] |
|
|
Stop snickering.
My gentoo machine slows to a crawl after a few days, it takes seconds to open a window. An eternity to close a tab on chromium. Stopping and restarting the browser helps a little. It's an i7, not a slow machine, 12GB RAM. The load is not high, the machine is not paging or out of memory ... just ... slow. Ordinary web pages like this one can't keep up with my typing.
Then if I restart KDE, all the performance comes back. The resource hogs I use are chromium and libreoffice, but I can't tell where the poor performance is coming from. At least when I'm running an emerge -e world, I can exactly see what's making my machine slow.
It's puzzling.
Is it possible somebody's mining bitcoin using javascript on my browser? Would that not show up on my load meter? some other kind of skullduggery?
Any helpful thoughts greatly appreciated.
Jesnow
Last edited by jesnow on Wed Mar 21, 2018 1:05 am; edited 1 time in total |
|
Back to top |
|
|
frebrd n00b
Joined: 26 Feb 2018 Posts: 3
|
Posted: Tue Feb 27, 2018 4:30 am Post subject: |
|
|
jesnow,
Few ideas:
1. performance can also be impacted by I/O, if you are using a HDD. Maybe Nepomuk, Strigi, Baloo and Akonadi are doing their thing? try disabling them if they are enabled. Also put your /tmp folder on tmpfs
2. What addons do you have installed on chromium? ublock and umatrix should block any unwanted javascript. Have you tried firefox?
3. (Unlikely for basic tasks) Is your cpu thermal throttling?
4. Have you tried using performance governor? |
|
Back to top |
|
|
mike155 Advocate
Joined: 17 Sep 2010 Posts: 4438 Location: Frankfurt, Germany
|
Posted: Tue Feb 27, 2018 8:33 am Post subject: |
|
|
Use top and iotop to find out which process(es) consume CPU time or I/O bandwidth. |
|
Back to top |
|
|
Juippisi Developer
Joined: 30 Sep 2005 Posts: 724 Location: /home
|
Posted: Wed Feb 28, 2018 6:59 am Post subject: |
|
|
Im having similar problems with Gnome3. If its up for 3 days, the UI gets laggy and every operation takes a long time. Relogging solves the problem.
I have 16 GB of memory and a powerful i7 processor so I doubt that's the problem. I did install iotop to monitor HDD activity next time (Im using SSD), so thanks for that tip. I do have htop installed and nothing is using memory or CPU a lot there.
Ive just pretty much lived with the problem. I used to believe its somehow NVIDIA-related because if I, say watch a twitch stream with mpv for 12 hours then Gnome starts feeling laggy earlier than 3 days uptime. |
|
Back to top |
|
|
NeddySeagoon Administrator
Joined: 05 Jul 2003 Posts: 54244 Location: 56N 3W
|
Posted: Wed Feb 28, 2018 9:41 am Post subject: |
|
|
jesnow,
Check your kernel.
$ grep COMPACT /usr/src/linux/.config
CONFIG_COMPACTION=y
Without that, it gets harder and harder for the kernel to dynamically allocate RAM.
It will page, by dropping code and reloading it, when that happens. That's slow, even on SSD. _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
Back to top |
|
|
dantrell l33t
Joined: 01 Jun 2007 Posts: 915 Location: Earth
|
Posted: Wed Feb 28, 2018 9:41 pm Post subject: |
|
|
Juippisi wrote: | Im having similar problems with Gnome3. |
This is a bit off topic since jesnow isn't using GNOME but the older the GNOME release version (in the 3.y.z series) the bigger this issue is. Which is to say it's almost certainly a GNOME problem.
The workaround is to restart GNOME Shell.
The fix is probably to spend a capricious amount of time plugging every memory leak under the sun. I don't know about you but I ain't got time for that. _________________ Dantrell B. |
|
Back to top |
|
|
Juippisi Developer
Joined: 30 Sep 2005 Posts: 724 Location: /home
|
Posted: Thu Mar 01, 2018 6:14 am Post subject: |
|
|
Quote: |
Check your kernel.
$ grep COMPACT /usr/src/linux/.config
CONFIG_COMPACTION=y
|
I did have this enabled, at least, but
Quote: |
Which is to say it's almost certainly a GNOME problem.
The workaround is to restart GNOME Shell.
|
Yeah, it hasnt bothered me that much. I switched from openbox to gnome3 and I could keep openbox up for weeks without it feeling laggy. But I understand comparing openbox and gnome is like comparing a 70s lada with a modern tesla, so...
Its just weird that if I look at htop it doesnt show that any process's memory usage has skyrocketed, or that any process has died. |
|
Back to top |
|
|
The Doctor Moderator
Joined: 27 Jul 2010 Posts: 2678
|
Posted: Thu Mar 01, 2018 6:40 am Post subject: |
|
|
I'd say that reflects on the quality of the development of the respective desktops. Memory leaks are the likely cause and those are likely from the innocent looking and easily forgotten desktop. _________________ First things first, but not necessarily in that order.
Apologies if I take a while to respond. I'm currently working on the dematerialization circuit for my blue box. |
|
Back to top |
|
|
krinn Watchman
Joined: 02 May 2003 Posts: 7470
|
Posted: Thu Mar 01, 2018 11:51 pm Post subject: |
|
|
Saw this kind of strange slowness one day : cpu not busy, ram all happy, but dns resolving was bad, and everything that was trying to resolve dns was having bad day trying server1, timeout, server2 timeout...
Just in case it help you, maybe you have the same case, someone after a few days change dns settings (dhcp or whatever network manager) and kde/gnome whatever DE do have a lot of name resolution to do and is slow waiting for an answer while it takes no cpu or ram. |
|
Back to top |
|
|
jesnow l33t
Joined: 26 Apr 2006 Posts: 856
|
Posted: Wed Mar 21, 2018 1:04 am Post subject: |
|
|
I was just looping back to say I found the problem in the dns performance. And guess what (see below)...
It's interesting that there is no benchmark I can find for dns performance, but it is now integral to every aspect of our existence. It was slowing down local "file save" dialogs, for example! Libreoffice internal operation slowed to a crawl. Text in Kwrite would wait several seconds to post. All because of a slow dns server. Seems like a pretty dramatic point of failure for all linux systems, and very hard to debug!
Jon.
krinn wrote: | Saw this kind of strange slowness one day : cpu not busy, ram all happy, but dns resolving was bad, and everything that was trying to resolve dns was having bad day trying server1, timeout, server2 timeout...
Just in case it help you, maybe you have the same case, someone after a few days change dns settings (dhcp or whatever network manager) and kde/gnome whatever DE do have a lot of name resolution to do and is slow waiting for an answer while it takes no cpu or ram. |
|
|
Back to top |
|
|
Hu Moderator
Joined: 06 Mar 2007 Posts: 21635
|
Posted: Wed Mar 21, 2018 1:10 am Post subject: |
|
|
Local file save dialogs should not be using DNS at all. If they are, somebody did something wrong.
How did you determine it to be caused by DNS? Were you using a self-hosted DNS server, one provided by your organization, by your ISP, or a generic Internet DNS server? |
|
Back to top |
|
|
pjp Administrator
Joined: 16 Apr 2002 Posts: 20067
|
|
Back to top |
|
|
krinn Watchman
Joined: 02 May 2003 Posts: 7470
|
Posted: Wed Mar 21, 2018 3:38 pm Post subject: |
|
|
Hu wrote: | How did you determine it to be caused by DNS? |
myself, by switching to another dns server.
I know some other slowness for gnome(2) (never used kde), but i try to keep them in mind (well, looks like i fail and forget them, because i no more use gnome, but mate, but mate must share gnome(2) troubles).
* gvfsd: but it's easier as you see it eating cpu cycles for nothing
* dbus: no need to figure out this is buggy, and applications may crawl to death waiting message bus answer
* locale: not the locale itself, but a badly set locale will bug dbus, gvfsd and other part of gnome, and once they are bug by something, see upper.
* bad resolution dns may also comes from no localhost set (something to remember because users love to edit /etc/hosts and trash localhost).
Yeah, that's what you get from getting old, experience
(and a bad memory which void experience) |
|
Back to top |
|
|
pallaert n00b
Joined: 29 Apr 2005 Posts: 26
|
Posted: Wed Mar 21, 2018 10:02 pm Post subject: |
|
|
Experiencing the same thing since a few days.
Using KDE & Chromium. For sure, this is related to chromium which shows an insane usage of GPU usage in Chromium's own process manager. However, when freezing happens, it's not just chrome, it's really everything!
I've seen a couple of X-related packages upgraded recently, I have the impression it's since I upgraded them.
Visiting some websites like https://giphy.com, with log of graphics, animation, it makes the problem very reproducible.
I had a www-client/chromium 64.xxx and have upgraded to 65.0.3325.146, unfortunately, upgrading didn't solve the issue.
I doubt it could be DNS related as that might indeed be source of slowness, but normally, not freezing all apps. _________________ Patrick ALLAERT
Open Source Web Developer
http://patrickallaert.blogspot.com/ |
|
Back to top |
|
|
Hu Moderator
Joined: 06 Mar 2007 Posts: 21635
|
Posted: Thu Mar 22, 2018 1:38 am Post subject: |
|
|
The original poster traced his problem to DNS. If you are confident that your problem is not DNS related, then you do not have the same problem. If you need help with a different problem, you should open a separate thread for it, since this problem has a solution and has been marked as solved, which tends to reduce traffic. |
|
Back to top |
|
|
Juippisi Developer
Joined: 30 Sep 2005 Posts: 724 Location: /home
|
|
Back to top |
|
|
sQu1rr n00b
Joined: 26 Jan 2014 Posts: 24 Location: UK
|
Posted: Fri Mar 23, 2018 6:10 pm Post subject: |
|
|
pallaert wrote: | Experiencing the same thing since a few days. |
Same here.
pallaert wrote: | Visiting some websites like https://giphy.com, with log of graphics, animation, it makes the problem very reproducible. |
Indeed it does, thanks for providing the link. I was sure it was chrome, but couldn't (and didn't have time/motivation to) test, now I know for sure.[/quote] |
|
Back to top |
|
|
sQu1rr n00b
Joined: 26 Jan 2014 Posts: 24 Location: UK
|
Posted: Sun Mar 25, 2018 3:26 pm Post subject: |
|
|
Has anyone solved it? |
|
Back to top |
|
|
krinn Watchman
Joined: 02 May 2003 Posts: 7470
|
Posted: Sun Mar 25, 2018 4:22 pm Post subject: |
|
|
sQu1rr wrote: | Has anyone solved it? |
main poster has mark the thread solve, so it is solve.
if you have a problem that cannot be solve as the main poster did, it's because your problem is different, so you're only doing noise there, create your own thread for your problem if you need help. |
|
Back to top |
|
|
jesnow l33t
Joined: 26 Apr 2006 Posts: 856
|
Posted: Mon Apr 09, 2018 10:44 pm Post subject: |
|
|
I noticed the worst slowdown was while running Libroffice along with chrome. which I do all the time. shut down LO, and chrome is back to normal. So I tracked it down to the Java runtime environment: Switch off the JRE and LO runs a million times faster and so does everything else. It was literally to the point where libroffce would leave a trail of windows across the screen when moving or resizing, and I could easilt get ahead of the typing buffer (!) when writing something like this post and have the text appears several seconds later.
turn off the JRE and it's not exactly snappy like it should be for a core i7 but much better.
JS. |
|
Back to top |
|
|
|