This is an archive of the Maximo Yahoo Community. The content of this pages may be a sometimes obsolete so please check post dates.
Thanks to the community owner Christopher Wanko for providing the content.
My infrastructure team built us new Windows 2012 Standard 64 bit virtual servers on VMWare using newly delivered Dell blade hardware, 8 GB RAM, Xeon E5-2670 2 processor CPU for our development Maximo 7.5 system. Compared to the 32 bit Windows 2K3 system (2 CPU, 10 GB) hosting Maximo 7.1 we have been running, a Maximo ear build is shockingly sluggish, taking from 20 to 40 minutes to complete where the prior system would usually complete in 2 to 5 minutes.
We are using WebSphere 7.0.0.35, same in both environments, but of course that is unlikely to be affecting ear build.
These systems are dedicated to Maximo, no other applications and no users as they are purely development.
Is this just Maximo 7.5 being different? Or is it likely there is some unrecognized system tuning issue that is slowing this machine?
Check to see if a virus scanner is checking every file on open...
Sent from my Verizon Wireless 4G LTE smartphone
-------- Original message --------
From: "jsteijn@gmail.com [MAXIMO]" <MAXIMO@yahoogroups.com>
Date:04/03/2015 9:20 AM (GMT-07:00)
To: MAXIMO@yahoogroups.com
Cc:
Subject: [MAXIMO List] buildmaximoear is slooow on new systems
My infrastructure team built us new Windows 2012 Standard 64 bit virtual servers on VMWare using newly delivered Dell blade hardware, 8 GB RAM, Xeon E5-2670 2 processor CPU for our development Maximo 7.5 system. Compared to the 32 bit Windows 2K3 system (2 CPU, 10 GB) hosting Maximo 7.1 we have been running, a Maximo ear build is shockingly sluggish, taking from 20 to 40 minutes to complete where the prior system would usually complete in 2 to 5 minutes.
We are using WebSphere 7.0.0.35, same in both environments, but of course that is unlikely to be affecting ear build.
These systems are dedicated to Maximo, no other applications and no users as they are purely development.
Is this just Maximo 7.5 being different? Or is it likely there is some unrecognized system tuning issue that is slowing this machine?
;-) Been there, done that, we <i>always</i> disable antivirus tools, at least the on-demand file scanners, while deploying because of the damage they do to performance. With scanner enabled build time is 4 hours or more. So the advice is excellent but that's not the issue here.
If I didn't know the guy who set up the server, and know he has this under control, I would guess that VMWare has the cpu throttled so it only looks like it's using all the cpu, with the real hardware only giving us a small part of its capacity. But we did that one in the last go-round too and know better.
Other than the version change, what else is different between installs? Are the resultant EARs from 7.1 and 7.5 roughly the same size? Did you explode each to compare what is being pulled in? Eliminate the obvious, like pulling in too much, check flags in the buildear command and especially look over the Ant script.
I would be using PSMon and FileMon on this; snag them from Microsoft if you haven't already.
-C
There is a known issue that IBM is in the process of documenting and will publish at some point but if you'd like to know the details on how to fix reach out to my previous client and he will share what IBM had them do to fix the problem. His email is mike.maina@duke-energy.com
Do you have McAfee Antivirus on your server? There's a known issue with that, which I discovered the hard way...
Shannon Rotz
Sent from my wonderful BlackBerry Z30 smartphone!
Original Message
From: sarahlockestewart@gmail.com [MAXIMO]
Sent: Saturday, April 4, 2015 8:04 AM
To: MAXIMO@yahoogroups.com
Reply To: MAXIMO@yahoogroups.com
Subject: [MAXIMO List] Re: buildmaximoear is slooow on new systems
There is a known issue that IBM is in the process of documenting and will publish at some point but if you'd like to know the details on how to fix reach out to my previous client and he will share what IBM had them do to fix the problem. His email is mike.maina@duke-energy.com
Symantec and it is disabled for initial setup and installation.