Author Topic: ArcaOS 5.1.0 and cups  (Read 922 times)

Dave Yeo

  • Hero Member
  • *****
  • Posts: 4496
  • Karma: +90/-1
    • View Profile
Re: ArcaOS 5.1.0 and cups
« Reply #15 on: September 19, 2023, 02:25:36 am »
It's an AMD? Most of what I said was for Intel. IIRC, with AMD, you have full integer cores and shared FPU, so different then Intel. Others can chime in with their experiences.
Sometimes the only way to turn off some cores is with ACPI parameters and then it is figuring out which are which as it is not always every second core.
As for Dooble, and the Qt5webengine, a lot of the problems are memory related, 4GB (actually closer to 3.5 GB) is just not enough memory for modern browsers. And of course the Qt5webengine is a work in progress, progress that hopefully will lead to the Qt6webengine.
I'd suggest running mem /v now and again to see how much memory, especially low shared is available and also consider raising your VIRTUALADDRESSLIMIT, perhaps to 2560 at first, then you could try 2816 and the max of 3072. How high it can go is hardware dependent, don't want to intrude on video memory as an example. The default is conservative.

Pete

  • Hero Member
  • *****
  • Posts: 1203
  • Karma: +8/-0
    • View Profile
Re: ArcaOS 5.1.0 and cups
« Reply #16 on: September 19, 2023, 04:30:43 am »
Hi Dave

Yes, AMD Ryzen 5 5600G - 6 cores but "12 processors initialised".


Already "tuned" using mem /v

Both reports are from immediately after boot:-
[H:\SYS\BIN]mem /v

Total physical memory:     14,271 MB
Accessible to system:       3,036 MB
Additional (PAE) memory:   11,235 MB

Resident memory:              183 MB
Available virtual memory:   1,225 MB

Available process memory:
  Private low memory:         375 MB
  Private high memory:        896 MB
  Shared low memory:          340 MB
  Shared high memory:         844 MB



After this modification to config.sys

REM **** VIRTUALADDRESSLIMIT=1536 - original line
REM **** The next line works best to reduce shared memory use
VIRTUALADDRESSLIMIT=2560


[H:\SYS\BIN]mem /v

Total physical memory:     14,271 MB
Accessible to system:       3,036 MB
Additional (PAE) memory:   11,235 MB

Resident memory:              183 MB
Available virtual memory:   1,225 MB

Available process memory:
  Private low memory:         375 MB
  Private high memory:      1,792 MB
  Shared low memory:          340 MB
  Shared high memory:       1,740 MB


Definitely an increase in high memory, will have to try larger values for VIRTUALADDRESSLIMIT and see what happens on this system - previous systems have not liked 3072 at all.


Regards

Pete






Dave Yeo

  • Hero Member
  • *****
  • Posts: 4496
  • Karma: +90/-1
    • View Profile
Re: ArcaOS 5.1.0 and cups
« Reply #17 on: September 19, 2023, 07:03:31 am »
Do you have the blocklist installed in Dooble? Helps cut back the ads, which usually are full of crappy JavaScript. Latest attached

Pete

  • Hero Member
  • *****
  • Posts: 1203
  • Karma: +8/-0
    • View Profile
Re: ArcaOS 5.1.0 and cups
« Reply #18 on: September 20, 2023, 02:32:05 pm »
Hi Dave

Seems to be a later file so, Thank You.


Regards

Pete

Dave Yeo

  • Hero Member
  • *****
  • Posts: 4496
  • Karma: +90/-1
    • View Profile
Re: ArcaOS 5.1.0 and cups
« Reply #19 on: September 20, 2023, 04:25:04 pm »
There's also now a dooble_filter list in dooble/Data from AdGuard DNS filter, seems to work importing it into the blocked domains, attached.