Poor dtr performance

[Former Member]

Hi,

when we do an activation of activities in the netweaver developer studio, we have an extremely poor performance, e.g. for a small change we wait up to 5 minutes in order to activate the change.

Now we have about 100 DC's in the dtr. When we started development in this track, the performance of the dtr was much more better than now.

A look at the server activity during an activation shows only an extreme cpu-usage, nearly no activity on the database or hard disk.

Did anyone encounter a similar problem or is this a standard behavior of the dtr.

Thanks for your help.

Achim

[htammen · Accepted solution]

Hi Achim,

I think that if you have 100 DCs you probably will have a high dependency relation between them.

So if you just make a little change to a file and check it in the CBS might have to checkout a lot of DCs out of the database into the temp. build folder.

Then all these jar files have to be read during the compile time.

Can the complexity be the reason for your problem? Do you have also long build times at your local PCs?

Regards

Helmut

[Former Member · Accepted solution]

Hi Helmut,

the build times at my local PC are very good (approx. 5 seconds for an average build).

Greetings.

Achim

[htammen · Accepted solution]

Hi Achim,

then the only reason I can think of is the transfer from and to the database. But there should be database activity then.

You could use the monitoring service of Visual Admin (or CCMS if Web AS is connected) to analyse the problem. The log files may also give some useful hints. Maybe there is a scheduled process that does not successfully finish and starts again each n seconds.

Did you install further services at the Web AS?

Are there other applications running at the instance?

Did you follow the hardware recommendations which are described in SAP Note 737368?

Regards

Helmut

[Former Member · Accepted solution]

Hi Helmut,

> Hi Achim,

>

> then the only reason I can think of is the transfer

> from and to the database. But there should be

> database activity then.

>

> You could use the monitoring service of Visual Admin

> (or CCMS if Web AS is connected) to analyse the

> problem. The log files may also give some useful

> hints. Maybe there is a scheduled process that does

> not successfully finish and starts again each n

> seconds.

>

> Did you install further services at the Web AS?

> Are there other applications running at the

> instance?

No to both.

> Did you follow the hardware recommendations which are

> described in SAP Note 737368?

Since this is still a test environment we would need 2 CPU's with 2 - 4 GB RAM. We have 1 CPU with 2 GB RAM.

This might be an explanation for the poor performance, but on the other hand only 2 developers are working with this machine and we don't have parallel activations.

So we will see how the performance is changing when we migrate to the productive machine which is fulfilling the hardware recommendations.

Thanx for your help.

Greetings.

Achim

[matthias_sohn · Accepted solution]

Hi Helmut,

- which platform (operating system and database) are you using ?

- did you ensure proper configuration according to OSS note 889038 and the notes referenced therein ?

- if you run on Oracle you should apply OSS note 848708 for proper database configuration

- did you ever update the database statistics ? This should be done on a regular basis to ensure that the database can find optimal execution plans.

- most DTR performance problems are caused by bad database configuration or stale optimizer statistics

- did you check how much CPU time / IO operations are consumed by WebAS / database processes on operating system level ?

- in Visual Admin you can analyse performance problems in the Performance Tracing Service. In the tab JARM you can find various breakdowns of application response time monitoring.

regards

Matthias