Well since the JVM can't allocate more than 2gb of memory on Windows it won't start if you set it higher. It looks like you aren't hurting for memory in those charts. You can (and I would recommend) upping the # of maximum requests based on these charts (low cpu, low memory usage). Now you may have to test it and see what would be the sweet spot on your box. I would double it and see how it performs and then review it and if the memory/cpu stays stable you could keep bumping it up until you see an issue there and then you'll probably get your box to perform well under concurrent load. Its more of an art/tweaking thing than it is a "set it to X" sort of a thing.
-Steve On Tue, Jul 20, 2010 at 10:52 AM, Ajas Mohammed <[email protected]> wrote: > Hi, > > I am attaching a snapshot of FusionReactor's system metrics page which > shows no. of requests/sec. Recently, it went to as high as above 24. > > We use CF 7 on Windows Server 2003, Intel Xeon CPU E5450 @ 3.00 GHZ, 3.99 > GB of RAM and the setting for *Maximum number of simultaneous requests is > set to default 8. > > *We have not changed any JVM Memory settings.* The **Minimum JVM Heap Size > (MB)* is blank and * Maximum JVM Heap Size (MB)* is 512. > > Anyone wants to share their thoughts on the setting for *Maximum number of > simultaneous requests, ** Maximum JVM Heap Size (MB) **or *any general > suggestions*?* Is it ok to up the Maximum no. of simultaneous requests? > > Thanks, > > <Ajas Mohammed /> > http://ajashadi.blogspot.com > We cannot become what we need to be, remaining what we are. > No matter what, find a way. Because thats what winners do. > You can't improve what you don't measure. > Quality is never an accident; it is always the result of high intention, > sincere effort, intelligent direction and skillful execution; it represents > the wise choice of many alternatives. > -- Steve Ross web application & interface developer http://blog.stevensross.com [mobile] (912) 344-8113 [ AIM / Yahoo! : zeriumsteven ] [googleTalk : nowhiding ]
