Public Discussions > General Advertisements

ArcaOS DVD and bootable USB stick available

<< < (11/12) > >>

ivan:
Hi roberto,

Will do when I reboot the computer in a few week time - it is on 24/7 until it starts to slow down.

Doug Bissett:

--- Quote ---But could you do the test to put 3760, and tell us if it works, or if at startup it tells you that you have an erroneous value and puts it by default.?
--- End quote ---

Since 3072 (2048 in old versions of OS/2) is the maximum allowable, 3760 should always tell you that it is invalid (does, for me). 3072 doesn't always work either, but it won't tell you that it is an invalid number. I don't remember what happens, but it isn't good. I always use 2560 (but 2760 should also work), just so I don't have to figure out if machines work with 3072, or not. 2560 seems to be sufficient for my needs, and leaves me with 1270944 bytes of upper shared memory (varies as I use it), after everything is loaded.

I have never seen anything drop upper shared memory below 1000000 bytes, yet (I may have missed it). Lower shared memory, on the other hand, is at 217856, with most things loaded. I have seen that drop to zero (with resulting catastrophe), when something (usually multiple videos in Firefox), starts eating it. However, with the Firefox TURBO thing, I haven't seen that happen recently. I also turn off media.autoplay.enabled in Firefox about:config, which has helped a lot. It means one extra click to play a video that I do want to play, but the rest don't start automatically.

Dave Yeo:
For a while I couldn't link xul.dll without having VIRTUALADDRESSLIMIT set to 3072. Eventually Mozilla changed the build process to not need as much memory.
As for the maximum value that works, it depends on how much of the (actual hardware) upper address space is taken by PCI devices and such.

Rich Walsh:

--- Quote from: roberto on June 19, 2020, 10:52:29 pm ---
--- Quote from: ivan on June 15, 2020, 10:49:11 pm ---[C:\]mem -v
...
Available virtual memory:   3,760 MB
...

--- End quote ---
I understand that you have the virtualaddresslimit of the config.sys in 3072, and it will work fine for you. But could you do the test to put 3760, and tell us if it works, or if at startup it tells you that you have an erroneous value and puts it by default.?

--- End quote ---

'mem' tells you how much physical RAM is accessible by OS/2. This has NOTHING to do with Virtual Address Limit which is a software concept unrelated to actual physical memory.

Every process has 4096mb of "virtual address space". The kernel always uses the top 1024mb of addresses from 3072 to 4096 mb. Virtual Address Limit determines how much of the remaining 3072mb a program is allowed to use.

ivan:
Thanks Rich,  I thought it was something like that from things I have read.  I thought I should satisfy roberto and try it but now I won't bother - rebooting the comp when things slow down is nothing more than using the reboot option from the xworkplace shutdown.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version