Governor Settings - Performance

[dssd]

How do governor settings help performance?

[MFGF]

They can prevent users from firing off long-running queries which kill the server or the database, and/or from retrieving billions of rows of data back into a report, and from writing reports which span more than a given number of tables.  All of these can help improve performance by stopping users from doing things which cause huge loads on the server, the database or the network.

MF.

[Kanag]

Hi MF,
         Can u please tell me where can i find Governor settings in FM??
Please tell me the tab where i can find Governer setting option..,

Thanks,
KR

[bvk.cognoise]

Hi dssd,

you will find governors settings in framework manager.
open framework manger project>after opening that project>in menu select  project menu> there you will find edit governors option>click on that

then change settings according to your requirement.


hope it helps you :)

thanks
bvk

[Arpitagrawal9]

Hi,

The Governor settings should always be set sensibly.For example,i prefer the Maximum Query Execution Time to be 10 minutes and the Maximum Number of Rows returned to 50,000 because if your report crosses these thresholds then either your query needs some serious optimization or in the latter case it is not suitable for analysis.

Hope this helps.

Thanks and Best regards,
Arpit
---------------------------------------------------------------------------------
Arpit Agrawal | InfoCepts | www.infocepts.com
Off: +91 712 224 5867, +1 301 560 2591, Mob: +91 996 047 2335
---------------------------------------------------------------------------------

[cognostechie]

I beg to differ on the latter because Cognos is not only used for Analysis but also for detailed reporting. In real life, lot of companies use Cognos for data dump which may require more rows than 50000.

[Arpitagrawal9]

I understand your concerns,Even i have created a cognos report for my client to dump all the data into excel,this is just an example

[hthakkar]

The governor setting should be set for a maximum of 30 mins i.e 1800 sec..that is the threshold limit supported or allowed by the Business Intelligence Center of Excellence(BICOE).That is for better performance and faster execution this needs to be followed.

Thanks and Best regards,
Hitesh
------------------------------------------------------------
Hitesh Thakkar | InfoCepts | www.infocepts.com
Off: +91 712 224 5867, Mob: +91 986 019 7135
------------------------------------------------------------.

[MFGF]

The governor setting should be set for a maximum of 30 mins i.e 1800 sec..that is the threshold limit supported or allowed by the Business Intelligence Center of Excellence(BICOE).That is for better performance and faster execution this needs to be followed.

Thanks and Best regards,
Hitesh
------------------------------------------------------------
Hitesh Thakkar | InfoCepts | www.infocepts.com
Off: +91 712 224 5867, Mob: +91 986 019 7135
------------------------------------------------------------.

If I'm being honest, I don't think it's necessarily a good idea to make a blanket statement that a governor threshold of 30 minutes needs to be followed.  Every situation should be analysed and a judgement call made on whether governors are required at all, and if so, what the appropriate setting should be.  I have a friend who works on a site where reports sometimes take hours to run, but because of the limitations and structure of the database and the requirements of the business, there is no other way around this.  For that situation, a governor setting of 30 minutes would prevent the business from getting the answers it requires.  I do agree that as a general rule of thumb it is desirable to prevent long-running queries though.  Just not in every single situation.

Just my tuppence! :)

MF.

[cognostechie]

Corrrrrreeeeeccccccctttttttt !! I totally agree.

There is only so much of 'Best Practices' that can be applied generally and lot of it is specific to the environment.

[RobsWalker68]

Hi,

There is one governor setting, Allow Enhanced Model Portability at run time   that it is worth checking you don't have turned on or you left turned on after an upgrade or a change of data source.

Leaving this on results in additional meta data call to the database instead of using the meta data cached in the framework

Rgds

Rob