Now that you have had a chance to read my outline of garbage collection tuning in java. You should be asking yourself how does this relate to my ColdFusion server. Or maybe you just wondered what Garbage Collection has to do with ColdFusion Servers.
So I'll start with a really quick overview of what garbage collection (GC) is. In Java your variables are represented as objects on the heap (the heap is the chunk of memory you allocate to the JVM), the objects are considered to be either alive (in use) or dead (out of scope, no references point to it). For instance when you have a
request variable, it is out of scope at the end of your http request (there is no way to access that variable again). So the Java Virtual Machine (the JVM) needs some way of freeing the memory that dead objects are taking up, this process is called garbage collection.
The first thing you might notice after reading the garbage collection outline is that ColdFusion MX 6.1 is using the throughput collector, or the parallel young generation collector (
-XX:+UseParallelGC) by default. If your ColdFusion server only has one CPU you may get better performance by using the default collector. If you have hyperthreading enabled CPU's you may be ok. If your server has multiple CPU's you may try tuning the number of threads that the parallel collector is using with
If you have 4 CPU's with lots of RAM you might want to try adding
-XX:+AggressiveHeap to your JVM startup options. You might also want to try this if you have 2 CPU's with hyperthreading enabled.
It may be a good idea to increase your
-XX:MaxPermSize=n if you have a lot of CFM files. Since each file is a class, you are adding a lot of class and method info to the perm generation.
Another thing you can try tuning is the sizes of the young and tenured generations. You can do this with the
-XX:NewRatio option. If you have a lot of cached, or persistent variables you will want to have a bigger tenured generation. But if your doing a lot of dynamic execution then you may be better off increasing your young generation.
Tuning is always about tradeoffs, and the specifics of your application, and your hardware.
- Robi Sen on Hung Servers, java.lang.OutOfMemory errors and Tuning CF JVM - November 19, 2004
- Tuning Garbage Collection - June 3, 2004
- OutOfMemoryError - GC overhead limit exceeded - March 25, 2010
- Visualize Garbage Collection - June 8, 2004
- ColdFusion Memory Usage Stats - March 15, 2004
Encapsulated in CFC's, the batch process executes a bunch of queries against a mySQL database schema, and outputs the results of minor computations into a text file. The process takes in excess of 15 minutes to run.
What I find is that after about 8 - 10 mins, the process starts to slow down, and CPU utilisation on the server takes a stepwize jump to 100 percent with little gaps. The gaps get further apart until finally the server grinds to a halt, and my only option is to restart the Cold Fusion service - if I can open up the services dialog that is. I have tried adding in calls to java.Thread.sleep(n) and while this has extended the time before it croaks, the result is pretty much the same.
I assume this is all caused by depletion of some scarce resource.
So, clutching at straws, I am wondering if attempts to tune the JVM GC will alleviate or cure the problem.
I am wondering if someone can help out with a pointer to a careful and evidence driven methodology of approach to performing such tuning.
- ColdFusion returning empty response with server-error: true
- Careful applying CF11u16, CF2016u8, CF2018u2
- Sessions don't work in Chrome but do in IE
- csrfVerifyToken does not invalidate the token
- The cf_sql_ is optional in cfqueryparam
- Cookie Expires / Max-Age 1969-12-31T23:59:59.000Z
- Burst Throttling on AWS API Gateway Explained
- How to Resolve Java HTTPS Exceptions