Re: Maximum shared memory for Informix 7.3 on SCO 3.2v5.0.5

MADS wrote:
Hi !!!

Yesterday I configured an instance of IDS 9.3 on RedHat and changed the
shared libraries base address, so now I'm using over 2GB of shared
memory for Informix with one million buffers

echo 0xB0000000L > /proc/$$/mapped_base
su -l informix -c oninit -v

IDS 9.3 on Linux is 32 bit (there isn't a 64 bit version) and so the most RAM you can possibly address is 4Gb or you run out of bits. If you've got over 2Gb shared memory and 1,000,000 buffers on a 2k page size you're over 4Gb which isn't possible without swapping. Your OS and other programs need to fit in somewhere as well. Am I reading your post correctly?

I also have an old SCO 3.2v5.0.5 with IDS 7.3, and I would really like
to use more memory for that instance, because I've been unable to use
more than 300000 buffers. Is there a way to change the shared libraries
base address on SCO 3.2? Maybe another trick to use more memory?

In SCO 5.0.5 you can change the kernel parameters by running scoadmin, selecting Hardware/Kernel Manager and then Tune Parameters. You then have to relink the kernel and reboot. However I don't recommend this or guarantee that a similar trick would work as on Linux where the change of mapped_base is in the machine notes from Informix. Is there anything in the machine notes for SCO? I would only follow what's in there.

Ben.
.

Relevant Pages

  • Re: Can a process start threads with individual user rights?
    ... I want to offer programming tools to a small group of ... UML wastes way too much memory). ... communicates with the web server program. ... Especially when you're allowing shared libraries rather than just "sandbox-able" interpreted code. ...
    (comp.programming.threads)
  • Maximum shared memory for Informix 7.3 on SCO 3.2v5.0.5
    ... Yesterday I configured an instance of IDS 9.3 on RedHat and changed the ... shared libraries base address, so now I'm using over 2GB of shared ... to use more memory for that instance, because I've been unable to use ...
    (comp.databases.informix)
  • Re: anyone understand torvalds critique of freebsd?
    ... Mach manipulate the VM page table mappings to make that page visible in the process address space rather than copying the sequence of bytes manually via a message-passing paradigm. ... The former approach tends to be more efficient for small amounts of data, especially for things smaller than one page of memory; the latter approach tends to better for things which are bigger in size. ... On the other hand, Mach was the first or among the earliest platforms to support shared libraries, dynamic loading of objects into user processes and into the kernel, and has somewhat better scaling in the face of gigabytes of RAM and VM usage than most Unix flavors do. ...
    (freebsd-questions)
  • Re: Close the application, shutdown the platform...
    ... > When we close the app, we shutdown the platform too. ... the native portions of Java are built upon shared libraries, ... you're not duplicating the library program code in memory ...
    (comp.lang.java.programmer)
  • Re: piplining principles (and confusion!)
    ... > Now, if you don't have a stack or known memory, then SMC ... This wastes BTB space. ... the lifetime of the program (i.e. generally shared libraries), ... will only be written to the swap file once unless they are being continually ...
    (comp.lang.asm.x86)