Hi,
I was wondering what is the ideal memory you prefer on an CF Production
server? We are running Intel Xeon CPU E 5450 @ 3.00 GHZ, 4GB RAM.
Any suggestions as far as If 4gb memory is good enough or it should be
greater than that for a production server?
Thanks,
Ajas Mohammed /
It could be. I'd be interested to know how many sites, what kind of traffic
each site brings, that kind of thing. But, if I had 4gb of memory, I'd set my
heap size to 1024mb. That is good enough usually unless you have a relatively
high-load server environment.
About 20 sites and high traffic site. I am not sure how many users though. I
guess there is a limit of 4gb memory on 32 bit systems.
I noticed lsass.exe is taking 600,000K of memory and jrun.exe is taking
193,604K of memory. So lsass.exe is using thrice as much.
Any suggestions?
Ajas Mohammed /
Are you currently experiencing memory issues? Judging by what you say here,
there may be some other issue going on besides what jrun.exe is using. But, if
you're not having memory issues and you've got it to spare, I'd say go ahead
and bump it up.
BTW, what version of CF?
We are on CF 7 windows server 2003. We are experiencing frequent slowness
and the only option left to us is restart CF service every now and then.
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
Then, yes, I would definitely set the heap up to 1024mb if it's not there
already. That should alleviate most, if not all, of the slowness.
On that note, one thing I've run into is that the session scope can become
quite obtrusive under load. Sites that carry a lot of session information with
Yeah, we are planning to use Fusion Reactor to monitor our apps. In our
case, its client variables used throughout i.e. no session variables at all.
I will definitely monitor pages that are running slow to see what is going
on but knowing hardware setup is also important. So I was just trying to
One thing to note, CF on a 32 bit Windows server can only be allocated 1280MB
of RAM... even if the server has 4 GB of RAM... you can only allocate 1280MB.
Anything higher than that, the service will not start. This is not true for CF
8.01 running on 64 bit operating systems.
Wes
From:
It won't improve the speed per se, but it will stop the slowness and loss of
http response caused by reaching your heap size maximum allowance. It will also
free you up from having to watch it so closely and keep you from having to
interrupt your client's service while you restart jrun.exe. It
One thing to think about along this line of thinking is if you set up CF in a
multiserver instance, you can allocate more ram to your heavy hitter by putting
it in its own instance, and then group your light sites under another instance
and allocate them their own memory as well.
yeah, thats a good idea. Unfortunately, we are so far down the road that I
doubt the management would not be willing to do separate instances. I love
that idea as it saves other sites from issues.
Wonder if someone chose that route after having issues with sites. It would
take lot of effort and
32 bit Windows cannot even fully address 4GB of RAM to begin with. The actual addressable amount is somewhere in the 3 1/2 ballpark. By the time you add in the other services allocations on there, it makes sense for the CF allocation to be around what Wes stated. From: Ajas Mohammed
Google is your friend:
http://lmgtfy.com/?q=maximum+coldfusion+heap+size+windows+32
Teddy R. Payne, ACCFD
Google Talk - teddyrpa...@gmail.com
On Thu, Jan 14, 2010 at 4:55 PM, shawn gorrell chees...@yahoo.com wrote:
32 bit Windows cannot even fully address 4GB of RAM to begin with. The
So, everyone here is pretty much on 64 bit systems? Just curious.
Thanks Teddy for the link.
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
Wow, guys, I would offer significant caution about a lot of the assertions
here.
It's NOT always true that increasing memory will improve performance. Not at
all. Indeed, there are times when increasing the heap could cause MORE
problems (and even just raising it from 512 to 768). It's too much
Charlie:
I have seen those errors before and would in the past, adjust both
java Vm settings and heap size in the BD admin console, as well as
MySQL settings. I did that over many months a few years back. Using
the same system today.
The settings I use now yielded the best results - no
To be clear, I wasn't referring at all to anything about you or setup
Derrick. :-) Still, as you're saying, yes there are also those kinds of
issues that can cause problems as well. Good that you've isolated a lot of
them.
That said, as for your moving to BD, I will argue that when some have
I for one appreciate your efforts!
OT - was asked yesterday during a bus dev call what is your site
built in/with that old saw. When I said cold fusion they chuckled.
This from a 26 year old. No matter. He asked what other sites are
built with CF. That old saw. Used to be a list but I am
18 matches
Mail list logo
