New Performance Settings and Improvements in 2004s

[Former Member]

Hi all,

I was wondering if there is a document or website with all performance settings that are

new

in BI 2004s (and that were

not

available in BW 3.5 or lower).

If this information is not grouped yet, I want to invite everyone to gather the 2004s specific performance information in this thread. The improvements that I'm aware of are:

• Write-optimized DSO: http://help.sap.com/saphelp_nw70/helpdata/en/b6/de1c42128a5733e10000000a155106/frameset.htm

• BI Accelerator http://help.sap.com/saphelp_nw70/helpdata/en/06/49c0417951d117e10000000a155106/frameset.htm

• Optimization hint for logical MultiProvider partitioning (native in BI 2004s) Note 911939

Of course there must be more.

Best regards,

Danië

[Vitaliy-R · Accepted solution]

Hi Daniel,

Great topic and good placeholder.

Another improvement is parallel (by partition) deletion of the data from InfoCube.

Will look for more with links later.

Cheers,

Vitaliy

[Former Member]

Note 1025307 - Composite note for NW2004s performance: Reporting

[Former Member]

Good note: 1025307.

Ravi Thothadri

[former_member313870]

Hi,

I tried looking for this parameter in se16 -- RSADMIN-- QUERY_MAX_WP_DIAG..

But this is not even available i.e this parameter is missing ..

Help.

Kapil.

[Former Member]

If you want to change the value to something other than the default value of 6, you need to run the SAP_RSADMIN_MAINTAIN program and specify the new value.

If you have never used this program, see if anyone else in your shop has, or run it in your dev environemnt first.

The pgm will request an Object and Value. For Object, you enter QUERY_MAX_WP_DIAG, and for Value, enter the new value you want to use. You then specify whenter you want to Insert, Update, or Delete, and in this case, you would choose Insert since there is no entry for QUERY_MAX_WP_DIAG currently.

[Former Member]

Thats correct.Try having it run on development strand first

Hope it Helps

Chetan

@CP..

[Former Member]

<b>Improving BIA indexing performance</b>

1) Navigate into the SAP_RETRIEVAL_PATH of a blade

2) Open the file TREXRfcServer.ini

3) In section [CONNECTION] add the following line

4)"index_package_size=200000000"

5) Save the file (using "Save to all hosts" to copy it to all blades)

6) Restart the TREXRfcServer(s) of your BIA Landscape

Hope it Helps

Chetan

@CP..

[Former Member]

Thanks for your input.

A wiki page sounds like a good idea. When I've got time, I'll try to create one with the info already posted in this thread.

[Former Member]

I would venture and advocate looking at peformance settings in

SPRO>Netweaver>Business Intelligence-->Performance settings

and then RSADMIN table entries.

Hope it Helps

Chetan

@CP..

[Vitaliy-R]

Hi Chetan,

I think we wanted to discuss here what is new in performance in BI7.

I think "Performance setting" is a new position in SPRO in 7.0, but it just calls most of RSCUST* transactions existed before.

But indeed RSCUST25 to RSCUST30 are new transactions in BI7.0:

RSCUSTV25	Database Interface/Performance
RSCUSTV26	Database Interface/Perf. (ORA)
RSCUSTV27	Set Standard Web Templates
RSCUSTV28	Determine Settings for Web Templates
RSCUSTV29	Settings for Web Template
RSCUSTV30	Load Distribution for Analys. Proc.

Feel free to correct me.

Regards,

Vitaliy

Edited by: Vitaliy on Feb 12, 2008 4:31 PM

[Former Member]

You are partially rite and you mentioned the new settings which come along with the aforementioned settings

Heres my take on few others -

<b>1)Tcode = RSODSO_SETTINGS</b>

used for Parallel activation of ODS to improve performance

<b>2)RSCUSTV25</b>

Query- SQL Split

Data mart Query Split

<b>3)se16-->RSADMIN</b>

DB_STATISTICS = OFF

OSS note 938040 - as per SAP

As of Support Package 8, the parameter is no longer used. This means that BI triggers the creation of database statistics, regardless of this parameter. The database itself determines whether the statistics are to be created or changed.

Tool BRCONNECT to be used after loading of all cubes.

<b>4)RSCUSTV8</b>

Reporting Lock = X

If you set this parameter to X, database commits are executed during master data activation. This prevents an overflow of rollback segments. Because temporary inconsistent states can occur here, reporting is locked during this time.

If you currently load large quantities of data in which many values change, leading to problems with the rollback segments, you should set this parameter.

<b>5)Parallel Processing of query</b>

Se16-->RSADMIN

QUERY_MAX_WP_DIAG = 6

https://forums.sdn.sap.com/click.jspa?searchID=4695392&messageID=2935804

<b>6)RSA1>Administration>Current Settings</b>

Here you get all the different independent areas which you can work to perk up the

performance related issues.

Infoprovider

DSO

Aggregate Parameters

BI system Data transfer

OLAP cache

Planning Locks

System Parameters

Batch manager

I luv to see my name popping up in wikipidea

Hope it Helps

Chetan

@CP..

[Former Member]

Seems like this would be better suited perhaps as a Wiki topic. Why not give it a try.