topic Re: Out of the box install maxes out CPU on Windows in Alfresco Archive

Out of the box install maxes out CPU on Windows

pbkoob — Tue, 23 Jun 2009 13:45:55 GMT

I have a straight out of the box install of Alfresco Enterprise 3.0 Full:Windows 2003 R2 Standard Edition SP2Oracle 10.2.0.42.27GHz Xeon on VMWare3.0 GB RAMThe only configuration I have made is to point the server to Oracle instead of using Derby.When I start Alfresco, it is running properly as far

Re: Out of the box install maxes out CPU on Windows

mrogers — Tue, 23 Jun 2009 15:32:16 GMT

Your first port of call should be to get Oracle off the machine running Alfresco. A database needs as much CPU as possible.

You may also want to detune alfresco for your small machine. Out of the box Alfresco is configured for an enterprise class machine.

You probably also need to look at your VMWare settings to make sure there's no memory paging going on. You may have a clash between VMWare's memory management and Java's memory management.

Alfresco runs on a machine smaller than yours, such as my laptop, without problem.

Re: Out of the box install maxes out CPU on Windows

pbkoob — Tue, 23 Jun 2009 15:52:33 GMT

Thanks for the quick response.

My oracle server is on a remote so I am ok there.

Detune alfresco? How much bigger should my machine be to be considered "Enterprise class." I will eventually have enterprise usage.

I'll have a look at the VM settings as well.

Re: Out of the box install maxes out CPU on Windows

pbkoob — Tue, 23 Jun 2009 18:50:49 GMT

The systems only uses 1/3 the system memory yet CPU is at 100% so there is no memory paging concerns.

Interesting.
I am not running alfresco as a Service yet the two big process running is java.exe at 65-80% of the CPU and services.exe which seem to run 20-35% of the CPU. They increase in tandem right after tomcat posts INFO [service.descriptor.DescriptorService] Alfresco Started

Re: Out of the box install maxes out CPU on Windows

mrogers — Tue, 23 Jun 2009 18:51:51 GMT

Does the load go down after a while?

Re: Out of the box install maxes out CPU on Windows

pbkoob — Tue, 23 Jun 2009 18:57:39 GMT

One more observation. When I shut down alfresco, the services.exe returns 0%, but Java takes up 96-98% of the CPU.

Re: Out of the box install maxes out CPU on Windows

pbkoob — Tue, 23 Jun 2009 18:59:40 GMT

The longest I let it run is an hour. I had to reboot the machine after that.

Re: Out of the box install maxes out CPU on Windows

mrogers — Tue, 23 Jun 2009 20:50:17 GMT

Something is not right.

You say you don't yet have any browser windows connected. Do you have any other connections to Alfresco?

In particular do you have any alfresco CIFS drives mapped?

Could you also confirm which version and service pack of Alfresco Enterprise you are using.

Re: Out of the box install maxes out CPU on Windows

pbkoob — Tue, 23 Jun 2009 21:02:22 GMT

Nope. No CIFS connection.

I am using Alfresco 3.1
The log says I am using 3.1.0 (142) schema 1008

Re: Out of the box install maxes out CPU on Windows

pbkoob — Fri, 26 Jun 2009 18:56:51 GMT

I have pulled some more experienced people in to help me get more useful information on the process and we have found two things.

After tomcat is fully started, the No Paged Kernel memory is steadily, and linearly eaten up by the java.exe process until the machine runs out of kernel memory at which time it becomes unresponsive.

The java.exe process is trying to Open Services for some reason, even though I am running this interactively from the alf_start.bat and not as a Windows service.

Any suggestions?

Re: Out of the box install maxes out CPU on Windows

pbkoob — Fri, 10 Jul 2009 13:49:10 GMT

I got this problem fixed. It turns out that I needed to install the Microsoft loopback adapter. I guess alfresco (java.exe) tries to talk with itself using Remote Method Invocation (RMI) (a fact documented in several locations) and without the loopback adapter (my conjecture) it never answers and keeps spawning connection attempts, chewing kernel memory until it runs out.

Everyone I know, who has related experience, seems to think this is strange. I am not sure why this is needed, I guess MS Windows 2003 SP2/VMWare does not have the Standard 127.0.0.1 or that is not what java is looking for.

Here are the instructions I used:
http://support.microsoft.com/kb/842561
I followed Method 2.