100% CPU utilization Issue

[Former Member]

We are facing issue with 100% CPU utilization in the portal OS level while we are running a Java Webdynpro application which uses HSSF API for excel file and MDM Java API for MDM.

Here MDM is used for Catalog repository for SRM shopping cart.

For this SRM-MDM integration to upload the catalog the supplier will provide the catalogs in the form of excel file.

We have build custom WebDynpro applications with HSSF API and MDM Java API, to upload the catalog content from excel file into MDM SRM-MDM catalog repository.

Before uploading into MDM, we run a validation process in Java, for this we are using HSSF API and Java Collection Framework and since this process is running in background , we uses Message Bean and JMS for triggering this process.

Currently we are experiencing a high CPU utilization when the validation process started.

We have tested with 1700 line items in the excel file and the response time in ideal condition(where no other applications/process running except the SAP standard processes) is 4/5 minutes but CPU utilization during that time is above 60%.

This is serious problem for our Go-Live as we expect huge no of Catalog upload initially and this application will also deploy and run in current corporate SAP portal where other applications also running.

The OS is Windows 2003 server 64 bit

The SAP Portal 6.0 SP15 and WAS is 640 with SP15

MDM is 5.5 SP 06 patches 3

HSSF POI API 3.2

Any help is this would be highly appreciated.

Regards,

Peru

[former_member197561 · Accepted solution]

Hi Peru,

"

We have tested with 1700 line items in the excel file and the response time in ideal condition(where no other applications/process running except the SAP standard processes) is 4/5 minutes but CPU utilization during that time is above 60%.

This is serious problem for our Go-Live ...

"

This is no problem at all. When processing is started of course if it is a CPU intensive processing (such as string operations, calculations, etc) then the CPU would be 100%. The CPU goes below only when there are pauses due to I/O operations, but if you do not have such in that processing, it would not go below 100% in that time interval.

The 60% average CPU usage which is required in the Go-live check is intended when we have short processing requests, executed by multiple concurrent users. In this case we have spikes at 100% when request is process and pause of CPU when request/reply is send to frontend. The 60% , as I already mentioned , is only required as average!

Best Regards,

Sylvia