There may be a issue with fragmentation. Check for Average Clusterign ratio in database properties.
Executed time for each command is not recorded in application log. (not essbase.log)
If you are on 22.214.171.124 there is undocumented setting which can record the elapsed time for each statement in a calc script.
This setting is global and not calc script specific which can lead to performance issues. It has to be removed once you are done with your testing.
thank you for your reply.Is there any way to track when the BR has run from any application log.so that will try to find out of all fixes which one has taken more time.
All rules that are run from Calc manager are recorded as INLINE. (BR name is not recorded)
Check the following Doc for more info,
How to Determine the Time Taken for Business Rule Execution for a Rule Run from Calc Manager Console or Calc Manager Command Line Client. (Doc ID 2267607.1)
If the rules belong to planning the info can be found in following log,
Compare the ese details with app log for more detailed info.