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
Speeding up action buttons
-
- MVP
- Posts: 3233
- Joined: Mon Dec 29, 2008 6:26 pm
- OLAP Product: TM1, Jedox
- Version: PAL 2.1.5
- Excel Version: Microsoft 365
- Location: Brussels, Belgium
- Contact:
Re: Speeding up action buttons
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?
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?
Best regards,
Wim Gielis
IBM Champion 2024-2025
Excel Most Valuable Professional, 2011-2014
https://www.wimgielis.com ==> 121 TM1 articles and a lot of custom code
Newest blog article: Deleting elements quickly
Wim Gielis
IBM Champion 2024-2025
Excel Most Valuable Professional, 2011-2014
https://www.wimgielis.com ==> 121 TM1 articles and a lot of custom code
Newest blog article: Deleting elements quickly
-
- Posts: 59
- Joined: Mon Jun 02, 2008 8:49 pm
- OLAP Product: TM1 Palo
- Version: TM1 9.x Palo 3.2
- Excel Version: 2003 2007 2010
Re: Speeding up action buttons
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
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
- Attachments
-
- TM1 Action Button.zip
- (7.31 KiB) Downloaded 288 times
-
- MVP
- Posts: 3703
- Joined: Fri Mar 13, 2009 11:14 am
- OLAP Product: TableManager1
- Version: PA 2.0.x
- Excel Version: Office 365
- Location: Switzerland
Re: Speeding up action buttons
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).
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).