on 06-15-2016 4:40 PM
Hi All,
We are in BW 7.4 sp 13. What we have noticed is that the query in the multiprovider runs faster compared to the same query rebuilt on composite provider. The query is exactly the same and returns the same number of records,the composite provider uses the same infoproviders( SPOs and cubes total about 20) as the mpro. It is built via the new modeling tools only and has only the Union operation. The query itself is not that complex.
The observation via RSRT is that, the DB time is always more in comp prov. Both queries use execution mode 3. The multiproivder seems to perform select from all the individual infoproviders parallelly whereas the composite provider seems to cluster these 20 infoproviders into 4 parallel processes as shown in the access counter field.
We are also able to observe 20+ dialog processes in sm50 that perform database procedure execution when the query on the multiprovider is executed and 4 dialog processes for the other query which seems to confirm the above behavior.
The composite provider does not seem to utilize the maximum allowable QUERY_MAX_WP_DIAG value in RSADMIN whereas the multiprovider seems to do so which seems to result in much better DataManager event 9000 performance. Has any one observed such a behavior. Any pointers to make the query on the composite provider perform atleast as better as its multiprovider counterpart.
Regards,
Manideep
you can open an incident, if it is really as you described, the developer should fix this issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Mandeep,
Is it possible for you to check the same with the query execution mode 6?
Regards,
Manpreet
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi ,
Here are our observations.
Multi Provider | Composite Provider | |||
Mode 3 | Mode 6 | Mode 3 | Mode 6 | |
Datamanager time | 3 secs | 3 secs | 5 secs | 10 secs |
Number of unique access counter values | 16 | 16 | 4 | 2 |
For the multiprovider the mode is not changing the number of parallel read access , whereas for composite provider, the mode 6 seems to utilize even less parallel reads than mode 3 and performs even worse. Anyway, which mode could be better etc might be another topic for now we decided to stick to mode 3 and query on multiprovder.
Regards,
Mandeep
User | Count |
---|---|
88 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.