CentOS - Aug 2019 - browsers slowing Centos 7 installation to a crawl

My video problems mentioned in a previous thread are gone,
though I do not know why.

Now my problem is that whenever I have a
browser open and an internet connection,
my Centos 7 slows to a crawl.
Chromium seems to be the least bad.
Sometimes it slows to the point that I cannot even move the mouse.
Even switching between virtual terminals takes a while sometimes.
When I get there, top generally shows me between two and five D states.
I've changed service providers lately.
The problem survived the change.
Some sites seem to aggravate the problem.
Most recently, a site tried to connect to c.amazon.adsystem.com .
I got the message waiting for c.amazon.adsystem.com .
I have that address in my hosts file as 127.0.0.1 .
ping finds it and pings.
nslookup does not:
> [hennebry at localhost ~]$ nslookup c.amazon.adsystem.com
> Server:		192.168.0.1
> Address:	192.168.0.1#53
>
> ** server can't find c.amazon.adsystem.com: NXDOMAIN
Whether the slow-to-crawl problem is related to the failure to redirect,
I do not know.
The former is clearly more important.
Any suggestions on how to diagnose it?
Any ideas on why chromium is waiting for c.amazon.adsystem.com
and how I can fix it?

-- 
Michael   hennebry at web.cs.ndsu.NoDak.edu
"Sorry but your password must contain an uppercase letter, a number,
a haiku, a gang sign, a heiroglyph, and the blood of a virgin."
                                                              --  someeecards

On Sun, 4 Aug 2019 12:38:29 -0500 (CDT)
Michael Hennebry wrote:
> Any suggestions on how to diagnose it?
What happens if you try downloading a large file with wget?

What happens if you try browsing some websites with elinks?

-- 
MELVILLE THEATRE ~ Real D 3D Digital Cinema ~ www.melvilletheatre.com

On Sun, 4 Aug 2019, Frank Cox wrote:
> On Sun, 4 Aug 2019 12:38:29 -0500 (CDT)
> Michael Hennebry wrote:
>
>> Any suggestions on how to diagnose it?
>
> What happens if you try downloading a large file with wget?
I'll try it.  My expectation is that it will work just fine *once it
starts*.
That is my experience with downloading using a browser.
In the case of wget, the issue will be typinng the command.
Suggestion for a file?  A Centos iso perhaps?
I'd look for it with a browser,  but it might take a while.
> What happens if you try browsing some websites with elinks?
What is an elink?

To handle my centos mail,
I ssh to the server with my mail and run alpine
as the ordinary user that I am.
ssh is running from virtual teminal 2
while virtual terminal 1 is crawling.

-- 
Michael   hennebry at web.cs.ndsu.NoDak.edu
"Sorry but your password must contain an uppercase letter, a number,
a haiku, a gang sign, a heiroglyph, and the blood of a virgin."
                                                              --  someeecards

On Aug 4, 2019, at 1:38 PM, Michael Hennebry <hennebry at
web.cs.ndsu.nodak.edu> wrote:
> Now my problem is that whenever I have a
> browser open and an internet connection,
> my Centos 7 slows to a crawl.
> Chromium seems to be the least bad.
> Sometimes it slows to the point that I cannot even move the mouse.
> Even switching between virtual terminals takes a while sometimes.
> When I get there, top generally shows me between two and five D states.

Are you sure you don?t have other processes or users running on the system?  It
only happens when you have a network connection?  It might also be swapping
heavily, check to see how much RAM you have.  Check the output of ?free?.

Look at the syslogs/journal when you?re logged in (in a terminal, run ?sudo
journalctl -xfl?).  You will see a lot of stuff printed, but it might give you
an idea of what?s going on.

--
Jonathan Billings <billings at negate.org>

On Sun, 4 Aug 2019, Jonathan Billings wrote:
> Are you sure you don?t have other processes or users running on the system?
It only happens when you have a network connection?  It might also be swapping
heavily, check to see how much RAM you have.  Check the output of ?free?.
Pretty sure.  I rebooted this morning.

top - 17:32:20 up 15:47,  6 users,  load average: 1.12, 2.55, 1.56
Tasks: 238 total,   3 running, 235 sleeping,   0 stopped,   0 zombie
%Cpu(s): 21.5 us,  3.5 sy,  0.0 ni, 74.1 id,  0.8 wa,  0.0 hi,  0.0 si,  0.0 st
KiB Mem :  2020144 total,    80436 free,  1416824 used,   522884 buff/cache
KiB Swap:  4883724 total,  3887864 free,   995860 used.   149092 avail Mem

   PID USER      PR  NI    VIRT    RES    SHR S  %CPU %MEM     TIME+ COMMAND 
27121 hennebry  20   0 1636444 218240  49920 R  29.2 10.8   1:31.01 chromium-b+ 
27132 hennebry  20   0 1673932 213652  55576 S   7.3 10.6   1:01.19 chromium-b+ 
26614 hennebry  20   0 1871712 104840  41084 S   3.7  5.2   0:26.78 chromium-b+ 
27186 hennebry  20   0 1495336 109988  47176 S   3.3  5.4   0:16.55 chromium-b+ 
27423 hennebry  20   0 1431484  87076  45928 S   2.3  4.3   0:08.33 chromium-b+ 
26647 hennebry  20   0 2685156 188444  27308 S   1.0  9.3   2:19.84 chromium-b+
  5962 hennebry  20   0 3617336 111096  19404 S   0.7  5.5   2:25.24 gnome-shell
27174 hennebry  20   0 1481508 114332  48276 S   0.7  5.7   0:07.88 chromium-b+ 
27257 hennebry  20   0 1439148  96572  52020 S   0.7  4.8   0:05.98 chromium-b+
  3483 root      20   0  374444  20432  13732 S   0.3  1.0   0:42.88 X 
23824 hennebry  20   0  753956  18272   6488 S   0.3  0.9   0:13.63 gnome-term+
     1 root      20   0  128404   4376   2484 S   0.0  0.2   0:07.65 systemd

Usually when I'm having trouble, there are at least two D's.
Of course, 'tain't as crawly as it often gets.

Mem:        2020144     1454904       76140      204764      489100      135004
Swap:       4883724      978480     3905244

> Look at the syslogs/journal when you?re logged in (in a terminal, run ?sudo
journalctl -xfl?).  You will see a lot of stuff printed, but it might give you
an idea of what?s going on.
I think this qualifies as interesting.  I have rather a lot of it:
Aug 04 17:28:20 localhost.localdomain chromium-browser.desktop[26614]:
[26647:26728:0804/172820.614816:ERROR:latency_info.cc(149)]
Surface::TakeLatencyInfoFromFrame, LatencyInfo vector size 102 is too big.

I found it with google, but all the entries froze chromium.

-- 
Michael   hennebry at web.cs.ndsu.NoDak.edu
"Sorry but your password must contain an uppercase letter, a number,
a haiku, a gang sign, a heiroglyph, and the blood of a virgin."
                                                              --  someeecards