----snip
eclipse -vmargs -Xmx

The value should typically be at least "128M" (128 megabytes).
Usually, "256M" (256 megabytes) is ample. You should not set this value to be
larger than the amount of physical memory on your machine.

-----end snip

The key here is the amount of physical ram you have. Don't exceed it.

From http://www.eclipse.org/eclipse/development/readme_eclipse_3_0_1.html

Andrew,

Just changed this value and will poke around to see if the client seems
snappier and faster as you suggest.

I'd been exclusively using the "basic" client on the laptop I'm using at the
moment, because it's only got 1 GB, and the "standard" client was barely
usable... bumped the setting you mentioned up to 512 and the difference is
palpable. Oddly enough, it doesn't seem to increase the memory utilization,
which was what I'd assumed this change would do...

Holy smokes, batman! I nudged it a bit from 256 to 1024 (2 GB of ram on board)
and this sucker flies like a winged, greased pig! Sweet!

I just changed it from 256 to 512 and it sure seems faster.

I just made this change on a 2gb machine , bumped the setting to 1024, my co-
worker and I both see some improvement

Awesome - it worked.

I'm an avid SameTime 8.x user. As much as it's a great IM client, the one thing
that I do commonly complain about is how slow it is.

After reading this article I got intrigued and thought maybe I can obtain the
same some sort of performance gain making a similar change to SameTime as it
also sits on top of Eclipse.

After peeking through a few hundred files I managed to track down the file that
manages the vmarg.XmX within SameTime.

It is located here:
C:\Program Files\IBM\Lotus\Sametime
Connect\rcp\eclipse\plugins\com.ibm.rcp.jcl.desktop.win32.x86_6.1.1.200711051602
\jvm.properties

Contents listed below

###############################################################################
# Licensed Materials - Property of IBM
# 5724-M20
# ? Copyright IBM Corp. 2006 All Rights Reserved.
###############################################################################
vmarg.Dibm.jxes.jar2jxeOptions=-Dibm.jxes.jar2jxeOptions=-nog
vmarg.Dosgi.java.profile=-Dosgi.java.profile=jclDesktop-6.1.profile
vmarg.Xdump=-Xdump:heap:events=user,request=compact exclusive prepwalk
vmarg.Xgcpolicy=-Xgcpolicy:gencon
vmarg.Xms=-Xms12M
vmarg.Xmx=-Xmx256m
vmarg.Xquickstart=-Xquickstart
vmarg.DjxeCacheDir=-Dibm.jxes.jxeCacheDir=${rcp.home}/rcp/jxes
vmarg.Dosgiext=-Dosgi.framework.extensions=com.ibm.rcp.core.logger.frameworkhook
,com.ibm.jxesupport


Similar to your article just change the "vmarg.Xmx=-Xmx256m" to
"vmarg.Xmx=-Xmx1024m" . Just make sure you close SameTime down before making
these changes.

I saw an immediate performance gain in the load time. Once loaded the UI seemed
a little snappier too. SameTime although still bloated is now alot faster than
it was.

Thanks for sharing this tip :)

-Derek Reynolds

Made this change now on two machines. One with 1GB of RAM I changed it to 512
and the speed difference is barely perceptible. However, on a 2GB machine
changing the value 1024 is amazing! Thanks for sharing!

Made a big difference in Notes, but only a marginal diference in Sametime
Client, standalone 801. Perhaps because I log into 5-6 communities its slower.
Still thanks for that, very cool.

I have tried is and it seems to work well. My question is why hasn't IBM set
this as the default? Is there a downside that anyone has seen?

I put that question in the 8.5 beta 2 forum. The property defines the cache
parameters for the garbage collection. Increasing the parameter may result in
freezes (worst case) when the collection is cleaned up. The property is
different on operating systems. Our Linux Standard C■ient 8.0.1 has 512M by
default.

first, I have not tried the setting myself yet. I does seem logical that
startup is better which as different users have suggested.

But beware tuning the JVM is not a simple as turning a knob.

One of the problems of raising the maximum Heap size to a large size is that
much time will be spent on GC later on. So you may get faster load times, but
when you have worked a bit with the Notes client it may in fact be slower than
with the smaller setting

Lots of GC is of course also happening if the heap is too small.

For the non faint-hearted you can dive into the JVM options here:

http://blogs.sun.com/watt/resource/jvm-options-list.html

brgds Jesper Kiaer

Holy crap... Notes 8 Standard is actually usable! THANK YOU!!!

It does not make any difference.

I have 2GB RAM, and tested allocating 1024MB as suggested in the procedure..but
makes no difference

So much faster!

I'm using IBM Lotus Notes 8.5 Revision 20081211.1925 (Release 8.5)
Standard Configuration under WinXP SP2 with 3GB of RAM.

I changed from 256 to 1024 and it is amazingly faster and it is not consuming
more memory. The 3 services created in the 8.x client are altogether using less
than 256.

Very good hint

I was curious to see how it would affect my laptop. It turns out the default
value 256 is already roughly 1/2 of my RAM of 576MB already. I really never
felt that the Standard client was all that unbearable to use. It was pokey
after the initial launch, but that is to be expected while it updates the
designs of my DBs. Thereafter, it's certainly useable. Can't wait to put it on
one of my other boxes that has some additional horsepower. I'm also running a
Pentium III XP Pro SP3 on this laptop (I like to stress my software so it knows
whose it's boss is).

BTW... I found my jvm.properties in the original location (pre 8.5.1) even
though I'm running 8.5.1. Go figure.

Tried it on my 4Gb Ram laptop - 256 and 1024, and it was 35 seconds to start
notes whatever configuration (including changing the xms setting). I also tried
2056 however that crashed notes while it was starting. I tested this after a
reboot so it was a cold start each time. I wonder why it affects some and not
others?

Just applied the vmarg.xmx (for now on known as Eclipse Xmas gift to me) it
runs twice as fast for me. Will try some more and get back if I run into
trouble. Thanks for the info Andrew!

- Very spiffy! I also set Xms to 256M, because that JVM-standard parameter
defines how much it starts with, where Xmx defines the maximum memory that JVM
can use. Working very well so far, though I haven't noticed an obvious speed
gain. (shrug) I may bump Xms to 512 later.
- Also based on standard JVM options, last I knew no JVM would use more than
1024M no matter what you set Xmx at, and in fact it may destabilize the JVM to
tell it more, but up to and including 1024 is fine. Could be remembering
incorrectly, but there it is.
- Thanks Andrew!

The best way to find jvm.properties file is to search My Computer for the file.
It will display all files in the search result and then modify from there by
double clicking and opening with Notepad.

Hi !

Am not able to find out (com.ibm.rcp.j2se) Can you please help me in this, If
came to know how to do it, I can educate to our team

Thanks
karthik

Interesting explanation and developer opinion:

http://www-10.lotus.com/ldd/nd85forum.nsf/7756aedc25e6d81285256324005ac76c/f238a
7248969ac30852577bb0043f473?OpenDocument

Not only did this improve my Notes performance (informal "test" showed about 3
times faster to open a note in Preview) it also seems to have fixed a bizarre
calendar problem where Notes was suddenly showing multiple instances of some
meetings. I shut down Notes, edited the field per the instructions, and now I'm
seeing normal calendar entries AND faster performance. It just doesn't get any
better than that !!

Thanks!
Karen Roberts

What is the difference between this parameter and the JAVAMAXHEAPSIZE in
notes.ini?

This is great. I never felt like my Notes ran slowly before. Now I see how
fast it can go. Thank!!

It Works.

anyone tries the sametime Fix?

It's official now, and they even tweek another parameter.
the IBM recommendation:
vmarg.Xmx=-Xmx1024m
vmarg.Xms=-Xms512m
vmarg.Xmca=-Xmca512k

Note the inclusion of Xmca, this parameter sets by how much the current heap is
increased if an allocation request makes it necessary to grow the heap. Must
test this but hope to be rid of seeming to hang designer...

check http://www-01.ibm.com/support/docview.wss?uid=swg21617708 for reasoning.