Hi Ralph, > Quoting lots having had a quick go at reformatting it. >
Oops! Sorry. Copying direct from Chrome report page copied a bit too much. > > > My old Acer Chromebook > > Model R11, circa December 2015, with a 1.6GHz quad-core Intel Celeron > N3150 CPU. Is ChromeOS release R44 the latest update? > > Wow.Not sure where you got that information from, I didn't see it in my post!? My Settings says Your Chromebook is up to date Version 78.0.3904.92 (Official Build) (64-bit) No mention of a R[0-9]+ release identifier but, from Googling, R44 looks like it's 2015 vintage. > has got really, *really* slow. Like, every time I change tab it > > re-loads the page. And If I am typing onto a page it lags several > > seconds behind. > > Is that a really simple web page with just a HTML textarea, or one > that's piled up with Javascript that runs on each keystroke? Is typing > in the location bar also similarly slow? > That's an interesting question. A plain old retro page https://www.quinapalus.com/cgi-bin/match will echo my text input back instantly. Entering text into the grid at https://www.theguardian.com/crosswords/cryptic/27979 <https://www.theguardian.com/crosswords/cryptic/27979#25-across> I might type 6-8 characters before the first appears. "Several seconds" might be a slight exaggeration. That is after having cleared cache and disabled the extensions and then re-enabled them. Just doing that, however, does seem to have improved things. Chrome is not (at the moment) doing a complete re-load of each tab when I select it - which it was doing yesterday. Just that makes a heckuva difference. > You've still got quite a few extensions running. > > Great Suspender and Text Mode were attempts to get round the problem by reducing the amount of active page memory. GS did seem to help up to a point. > > Filesystem 1K-blocks Used Available Use% Mounted on > > /dev/root 1834352 1813120 21232 99% / > > This is a read-only filesystem that doesn't normally change thus its > size is just big enough for the content. > > Ah. Did not know what /dev/root was for. Google was not helpful. > /dev/mmcblk0p1 10801712 5520820 4712472 54% > /mnt/stateful_partition > This is where most of your data ends up. > Yep. Which is not under stress at the moment. > > > /dev/mmcblk0p8 11760 24 11412 1% /usr/share/oem > > > > 5. swapinfo seems ok... > > > > swap_info > > Filename Type Size Used Priority > > /dev/zram0 partition 4095996 879972 -1 > > low-memory margin (MiB): 101 778 > > min_filelist_kbytes (KiB): 400000 > > extra_free_kbytes (KiB): 0 > > > > edited highlights of system_files: > > 2.1G /home/ > > 1.9G /mnt/stateful_partition/ > > > > top memory use: high load average but low CPU > > top memory > > top - 13:29:10 up 15:56, 0 users, load average: 2.20, 5.75, 6.30 > > You've four cores, so presumably anything over four is CPU bound? > > > Tasks: 273 total, 1 running, 272 sleeping, 0 stopped, 0 zombie > > %Cpu(s): 10.3 us, 12.8 sy, 0.0 ni, 76.9 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 > st > > 10.3 + 12.8 = 23.1% so almost one of the four cores is permanently busy, > if it is doing all the work. And if it's a single-threaded thing > burning CPU then it may be just one core. > > > MiB Mem : 1946.2 total, 425.0 free, 862.8 used, 658.4 buff/cache > > MiB Swap: 4000.0 total, 3308.7 free, 691.3 used. 765.3 avail Mem > ... > > I am reluctant to install developer mode on the chromebook as that > > will involve a powerwash factory reset and I have a few chrome > > extensions I quite like, and stuff squirreled away in downloads that > > I don't want to have to mess around with uploading to elsewhere. > > > > ANyone else have any idea on what I can do to remedy this ? Just > > finding out what's happening and why would be a start. > > Given my normal machine for Firefox is a quad-core 1.8 GHz Intel > Atom D525, I'd blame extra code running in the browser, e.g. Javascript > for particular sits, and extensions. NoScript helped a lot here. :-) > Does ChromeOS offer an about:about index of what there is to peruse, > e.g. about:serviceworkers? Or performance monitoring by tab? > I do have a chrome://serviceworker-internals/ which gives me a set of sections like: Scope: https://mail.google.com/mail/u/0/ Registration ID: 207 Navigation preload enabled: true Navigation preload header length: 4 Active worker: Installation Status: ACTIVATED Running Status: RUNNING Fetch handler existence: EXISTS Script: https://mail.google.com/mail/u/0/sw.js?offline_allowed=1 Version ID: 9560 Renderer process ID: 10434 Renderer thread ID: 7 DevTools agent route ID: 31 Log:[ empty text box] [Stop] [Inspect] [Unregister] The above is the only one in RUNNING state, the others were all STOPPED. There were only 5 in total, _not_ mapped 1:1 with open tabs. I guess if things got really laggy I could try Stopping individual running workers. > > I'd disable as much as easily possible to return to the Chromebook's > more original state, knowing you can re-enable them easily too. See if > that helps, and gradually bring things back. Web sites keep placing > ever more load on the browser as developers often have the latest > hardware, e.g. https://www.indiehackers.com/group/amas Agreed some devs assume that everyone has the highest spec client machine. The Task Manager lets me see the total memory footprint of each process, its CPU consumption and JavaScript memory: > GMail is using 157,744K of Javascript memory as I write; LastPass and AdBlock are eating 20MB and 90MB in round numbers respectively, my Guardian Crossword uses 40MB just for JavaScript. But the overall sum of memory footprints should still be well under the 2GB available. Thanks, Victor -- Next meeting: BEC, Bournemouth, Tuesday, 2019-12-03 20:00 Check to whom you are replying Meetings, mailing list, IRC, ... http://dorset.lug.org.uk/ New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
