Skip to main content

Reminder: Increase the maximum available memory on your Lotus Notes client JVM today!

Yup, that's right.  Public Service Announcement time.

If you haven't increased the maximum memory available to your Lotus Notes JVM yet, what are you waiting for?

By default, the Notes JVM only has 256mb of memory available to it.  On a system with 4GB+ of memory, you should be easily able to increase it to 1/4 to 1/3 of the system memory and improve the end user performance.

Here's how:

  1. Shut down Lotus Notes.

    • In order to make sure that all processes are stopped, run this command:

    •  Start -> Run

  2. Type:

    • C:\Program Files (x86)\IBM\Lotus\Notes\nsd.exe -kill

  3. Open:

    • C:\Program Files (x86)\IBM\Lotus\Notes\framework\rcp\deploy\

  4. Open the "" file in a text editor like notepad.  You will possibly require Administrator permissions.

  5. At the beginning of the file, you will see text surrounded by a lot of pound signs ####.

  6. The first ‘property’ after the last # sign is:

    • vmarg.Xmx=-Xmx256m

  7. Change 256m to 1024m so that the line reads:

    • vmarg.Xmx=-Xmx1024m

  8. Save your changes and close the file.

Restart your system, and experience the difference.


  1. In case anyone wants to see this in action.  I did a video on this as well as some other domino designer tips for NotesIn9.

  2. IMHO you should not only increase Xmx (maximum Java heap size) but Xms (initial Java heap size) too. If you want to reduce memory allocation then consider increasing Xmca to more than the current 8Kb.

    And for smoother garbage collection I would suggest you to change the following entries with a new value:


    Have a look here -> <- if you need to understand how the IBM JVM allocates memory.

  3. Watch out for updates/fixpacks. They all replace the file, so the values go back to the defaults and you have to remember to increase them again.


Post a Comment

Popular posts from this blog

Policies and Controls are King in the IT Security world

I came across an article by Roger Grimes over at Infoworld on how security policies and controls are the real power when it comes to IT security. Roger mentions the SANS 20 Critical Security Controls for Effective Cyber Defence , which are a great read for anyone looking at updating or auditing your policies for completeness. The SANS top 20 controls are a must for any organization: Inventory of Authorized and Unauthorized Devices Inventory of Authorized and Unauthorized Software Secure Configurations for Hardware and Software on Laptops, Workstations, and Servers Secure Configurations for Network Devices such as Firewalls, Routers, and Switches Boundary Defense Maintenance, Monitoring, and Analysis of Security Audit Logs Application Software Security Controlled Use of Administrative Privileges Controlled Access Based on the Need to Know Continuous Vulnerability Assessment and Remediation Account Monitoring and Control Malware Defenses Limitation and Control

Error 217 - Error creating product object on Domino 64 bit

I'd like to share something with you.   An error that you'll get if you are trying to use ODBC with Domino 8.5.1 64bit. It starts out with an agent error of Error 217.  The text of the error is "Error creating product object" You can read about it here on the Notes/Domino forum . You can find the solution here as well . I guess I'm now waiting for Domino 8.5.2 for a solution for this.   It would have been nice to have had this in the release notes.  It would have help me greatly.

Fun Little Earthquake

It's 1:45pm EST in Ottawa, Ontario, Canada. We just had an earthquake.  Not strong enough to damage anything, but enough that I watched people run out of buildings. What a fun Wednesday.