Does anyone tested how much memory 8.0.1 x64 could use? What effect does it have to performance?
Thanks.
Subject: 801 2Gb limit
I’ve tested 801x64 on powerful server. It have used only 2Gb of RAM. 
Subject: Ah!
So regardless of how much RAM is on the system domino is only using 2GB. Couple of questions:
-
Is this all Domino processes combined?
-
How do you know that Domino is using only 2GB of RAM? What tools are you using?
Subject: It would be very helpful for us to get answers to these questions
We know there are issues with the file system cache but aren’t aware of any other problems. If there are then we need to know where to look. Thanks!
Subject: Thanks Jim
Thanks for the concern and willingness to help, Jim. I do recall that a lot of what we saw was web-server-related limitations back in the ND6.x days. I know that a lot of it was private-handle-related (where you’d run out of private handles long before running out of system or process memory). ND7 changed some private handle routines (e.g. DXL importing) to public handles, which helped some in our case.
Does ND8 still use private handles at all? If so, can you detail which areas specifically were changed from private to public in the transition from ND7 to ND8? With those in mind we can “open up” our caches and other settings here and test the limits to see what we get memory-consumption-wise.
Subject: I believe 8.0.1 still has a 2GB limit.
Here’s what I know:
ND 8 removed the last of the internal 16-bit memory handlers from core Notes. 8.0.1 is the first release to support 64-bit architecture, but from what I know it doesn’t yet take advantage of it. The goal (as far as I know) was to first “do no harm”. From 8.0.1, it should be pretty straightforward for the dev team to begin leveraging 64-bit hardware advantages.
If I had to guess, though, we won’t see Domino use any of those advantages until 8.5, or possibly the version after that. If it does pop up during the 8.0.x codestream, it will probably be some sort of INI setting that you have to turn on, and would be “unsupported” initially.
Subject: 4Gb out of the box
32bit applications built in LARGE_ADDRESS mode (which Domino is) get automatic access to nearly the entire 4Gb address space with no modifications or configuration. This is similar to using the /3gb boot flag in Win2003, only better. Most of the operating system takes advantage of the 64 bit address space, leaving most of the 4gb process space for the application. It isn’t exactly contiguous though, because Windows loads some libraries right at the beginning of the second half of the address range, but that’s not really a problem because that still leaves nearly 2gb of contiguous “extra” space in the previously unusable upper address range. It’s a big win!!
Subject: This definitely hasn’t been the case according to numerous reports…
Is that new to ND8? We’ve got servers here that have 4GB of RAM and only run Domino, and Domino never consumes more than 2GB.
Subject: Confusion?
When I refer to 4Gb I mean address space per process. You are referring to 4Gb of physical memory on the system. They are 2 completely different things. There is lots of information about virtual memory management, this one for example: Managing Virtual Memory | Microsoft Learn
The 2Gb memory limit must have referred to address space (that’s the common reference) since Windows 2003 Standard Edition can use up to 4Gb of RAM and newer versions can use much more (see here: Memory Limits for Windows and Windows Server Releases - Win32 apps | Microsoft Learn)
Subject: 8.0.1 and 2GB Limit - What about Solaris
Most of the discussion about increased memory limits centers on Windows servers.
With our primary email servers running on Solaris 10/SunFire v490s, I’m wondering how these changes impact our environment.
Our servers have 16GB RAM and Solaris has been running in 64 bit mode for years.
Do we need to do anything or has Notes on Solaris taken advantage of this already?
Subject: Unlikely to affect Solaris
There haven’t been any real changes. There is some question of what exactly is meant by “2GB memory limit” in Windows, but you are correct that Solaris has been a 64 bit operating system for years. In addition the process address space in Solaris is nearly the entire 4Gb (for 32bit processes) which helps prevent memory issues in that arena.