cancel
Showing results for 
Search instead for 
Did you mean: 

VC 7.0 - Performance during query execution

Former Member
0 Kudos

Hi Experts,

we have built an VC cockpit wich includes ~35 Querys.

When the user opens the cockpit the VC modell starts all 35 querys.

When we start the querys in the SAP BI System (RSRT) they all need less than 1 sek each.

Our BI system is able to handel 40 querys simultaneous.

Our problem is that the cockpit need ~40 sec. until all querys have been finished.

We suppose, that the VC starts all querys seriell instead of parallel.

Is there any configuration where i can switch between parallel and serial mode?

Thanks for your help

Regards

Florian

Accepted Solutions (0)

Answers (1)

Answers (1)

0 Kudos

Hi,

We are experiencing the same issue. Did you ever get a response or workaround? I have opened a message with SAP on this issue. What SP level is your system at?

John Dobbins

Former Member
0 Kudos

Hi

We also have the same problem.

Our workarownd was redesign UI of VC model and split it to number of different iViews.

Please post the solution if it existing.

Ola

Former Member
0 Kudos

Hi,

exactly this was also our way to solve the performance problem.

Redesign the VC model and split the querys in different i views. In the end we decided to start the iview not simultaneously. Instead we put them into a row and start them step by step.

But i think thats only an workaround.

^^ Regards

Florian

Former Member
0 Kudos

Hi,

I am also facing the same problem, did you get any workaround?

Regards

Pramod

Former Member
0 Kudos

... there is no reasonable workaround while using VC 7.0.

^^ Just change the conceptual design of your application. Thats the easyest way to make your customers happy.

Regards

Florian

Former Member
0 Kudos

Did enybody know if this problem sloved in VC 7.1 / VC 7.1.1 ?

And if yes, so how?

Former Member
0 Kudos

SAP consultans told me, that in VC 7.1 you can define parallel pipes for each query. So it should be solved.

^^ In our company we are not able to check this because we just have VC 7.0 installed.

If anyone can confirm the statement of the SAP consultants - please do it

Redards

Florian

Former Member
0 Kudos

Hi all,

we've also faced the same issue and we consider to split our cockpit in n VC model / i-view; we have for each model at maximum 36 queries splitted in 10 i-view:

  • 1 i-view for global pictures of all KPIs

  • 9 i-view for the graph detail, 3 graph views so 3 queries below, of each KPI

When i run my dashboard it takes only 15 sec for run all 36 queries.

The tips that we've considered is to adopt small query (with selection on month timeframe) for the first global i-view.

Rob

Former Member
0 Kudos

Hi all,

There is an option 'Use dedicated connections for nested iViews' in Tools > Options > Compiler Tab.

If u put each Data Service in separate nested iView prformance will be better.

Plese, let me know if this sloved the problem.

Ola

Edited by: Ola Agiv on Mar 22, 2009 8:08 AM

Former Member
0 Kudos

We have tried this option - but there where no better performance at all...

Not as supposed the VC application only use one connection.

Regards

Former Member
0 Kudos

Hi Florian,

Did u use nested iView for each Data Service?

Which SP u use?

Ola

Former Member
0 Kudos

Hi Ola,

yes we use nested iViews with SP 18.

Regrads

Florian

mark_moshkovich
Participant
0 Kudos

Hello,

Using the dedicated connection for nested iViews feature, was good thinking.

But - since the execution time of your queries is relatively short compared to the overall time for the "running a query" process, i.e. the HTTP request for execution, creating the connection on portal side, executing the query, returning the result and displaying it on the Flex runtime. --

all the other factors in this equations takes more time (relatively) than the query execution itself. (~1 seconds).

That is the reason why you don't observe major changes between running your 40 queries on a single connection or on multiple connections.

This feature was intended for queries that run for a long period of time. (tens of seconds or minutes)

in such queries, you will see the difference.

Mark,

Visual Composer 7.0 development and maintenance team.