Xbatch jvm parameter?
Copy link to clipboard
Copied
I'm trying to track down the reason for a newly deployed CF9 server's performance being
poorer than that of our existing CF9 server, even though it is a beefier server running a 64 bit OS a
nd 64 bit CF. One of the differences I noticed is that the older server never got the
9.01 or hotfix applied to it, but the new one did, and the new one has an additional JVM paremeter "Xbatch" that presumably came along with 9.01
Anyone have info on the impact of Xbatch on CF and it's performance? It seems to control whether Java does compilations in the backgroud, but I cannot relate that to how that might impact ColdFusion.
thanks
-reed
Copy link to clipboard
Copied
Hi Reed,
This is what I have noticed and am indeed curious when CF8 and CF9 (Standard or Enterprise) install on Windows 64bit the CF JVM arguments in part end up with –Xbatch in the settings. Why is Xbatch there on 64bit and not 32bit? What does it do? Is there some performance (or un-performance in keeping with other posting) benefit (loss) with it? Can I safely run CF on 32bit with Xbatch? What is being compiled?
The CF\runtime\ jre\bin\server\ Xusage.txt says:
-Xbatch disable background compilation
Other online Java manuals expand on that and say:
-Xbatch
Disable background compilation. Normally the VM will compile the method as a background task, running the method in interpreter mode until the background compilation is finished. The -Xbatch flag disables background compilation so that compilation of all methods proceeds as a foreground task until completed.
Certainly on 64 bit if I take Xbatch out of the JVM args and run CF it will work for a while however after some load will become unresponsive. I have not done any significant testing CF 32bit with Xbatch included in JVM args other than noticing CF runs up.
HTH, Carl.
Copy link to clipboard
Copied
Hi Reed,
No takers here. Maybe should post in server administration?
Regards, Carl.

