Page 1 of 1

Speeding up action buttons

Posted: Thu Oct 15, 2009 6:08 pm
by Kaveenga
Hi All

Would appreciate your help and suggestions on this one.

I am trying to use an action button in a worksheet to allow users to trigger a process. However, it takes 50-60 seconds before it even asks the user to confirm running the process.

Can anyone provide a suggestion?

Many thanks

Kavee

Re: Speeding up action buttons

Posted: Thu Oct 15, 2009 7:59 pm
by Wim Gielis
Hi

What happens in the process?

What is the data source of the process?

When executed in Perspectives or Architect, how does the process work there?

Re: Speeding up action buttons

Posted: Thu Oct 15, 2009 11:30 pm
by Kaveenga
Hi Wim

The process kicks off a data transfer between 2 cubes. Nothing complex.

Running the process in Server Explorer take about 40-50 seconds. However, using an action button introduces an additional 50-55 second overhead.

I've recorded the screen of TM1Top. The recording started a second before the Action Button was clicked. The actual process starts at second 56 - for the first 55 seconds TM1 is performing some other stuff.

Regards

Kavee

Re: Speeding up action buttons

Posted: Thu Oct 15, 2009 11:59 pm
by lotsaram
I have also noticed that when executing a TI via an action button the process can sometimes take much much longer to execute than if the same process is executed from server explorer. In my opinion this is a definite bug but I am not aware that IBM have acknowledged that a defect exists or whether there is already an outstanding SR for this issue.

The extended "object duplicate" thread activity in top that you have recorded before the process even starts executing is the same thing that I have observed previously. What exactly this means and what exactly the server is doing and why it only happens when a process is called from an action button, I am none the wiser.

A workaround is to execute the process via VBA which will then give the same performance as executing via server explorer, but this requires quite extensive coding (if you haven't done this before) and some knowledge of the VB API and will work only in Excel and not on TM1 web. (and obviously this is exactly the sort of thing action buttons are supposed to avoid).