locked
Delay showing changes in a graph after Cube Processed RRS feed

  • Question

  •  

    Hi folks,

     

    I have faced this issue over and over, project after project regarding proclarity views.

    After I manually processed the cube it takes a little while, something like 10min or so,  to show the changes in Proclarity views inside a SharePoint site. Is there any attribute to set anywhere to make it faster?I mean, any cache to disable or something? Is it a proclarity or a sharepoint issue?

     

    thanks for your time
    Wednesday, February 27, 2008 1:28 PM

Answers

  • HI Tyagi,

    It's likely an issue with the PAS cache taking that ten minutes to be invalidated following the cube processing.  If you need the most up to the minute information from the cube, it is possible to disable the cache entirely at the PAS layer, but you may notice a performance hit.  Caching can be disabled in the PAS global.asa, which is located by default at $\Inetpub\wwwroot\PAS.

     

    "...there are several settings in the Global.asa file that controls how the PAS Cache Engine works for each installation.  All of the defaults have been set at levels where the broadest performance level can be maintained, but in different installations these settings may need to be changed to increase performance and change some behavior.  Below is a list of each setting, what it does, and the applicable values.  Please note that these are the available settings for Cache Engine, and were based on the n 6.3 version of PAS.

     

    AutoInvalidateTime – This is the amount of time it takes for a cache entry in the cache to be flagged as ‘Invalid’.  By default this is set to 600 seconds or 10 minutes.

     

    Cache.LeasePeriod – This setting is used to flag each cache entry in the engine for the amount of time they may be used before they are automatically removed.  By default this setting is set to 21,600 or 6 hours.  Whenever a cache entry is re-used this timer is reset.

     

    Cache.SpaceLimitMB – This is the amount of hard drive space the cache entries can take up before the oldest entries begin to be ‘Invalidated’.  This is sometimes called the ‘Soft Limit’ since even though the files are invalidated; they still reside on the hard drive.  By default this setting is 512mb.

     

    Cache.HardSpaceLimitMB – This is the amount of hard drive space entries can take up before they are purged from the HD.  The oldest invalidated entries are purged first and then so on and so forth.  By default this is set to 1024mb.

     

    Cache.RelativeDirectory – The physical file directory where the main ‘cache’ folder is located.

     

    Cache.QualifiedDirectory – This is the directory string used by certain parts of the PAS code.  Notice that the application variable, “QueryPath” is used to help create the string.

     

    Cache.EvictionThreadTimeIntervalMS - This setting determines how often the thread to clean up the PAS entries is run.  By default this is set to 30000ms.

     

    Cache.HitRate = Sets the target hit rate of the cache engine. By setting to zero, effectively turns the cache engine off.  This setting was initially put into the system as a developer troubleshooting setting, but was left in to facilitate the ability to turn the Cache Engine off.

     

    Cache.StatsInitializationFile - The StatsInitializationFile property returns/sets the name of the file which initializes the statistics gathering. By default, this file is ...\Inetpub\wwwroot\PAS\CacheEngineStatsSetup.xml."

     

     

    Hopefully this helps you achieve the desired behavior.

     

    -Bob

     

    Wednesday, February 27, 2008 6:18 PM
  • Some have also chosen to deal with this as part of their SSIS package.  That is, they run the task to process the cube, and then run a task to clear the PAS cache.  Check out this post for a code sample of what the console app used in that task might look like.

     

    If you are doing things manually, you can just open the PAS Admin Tool, right-click, and choose to clear cache.

     

    You do have the ability to disable the PAS cache in the global.asa file in the PAS directory, but we recommend this only for troubleshooting, as doing this permanently will likely severely impact your performance and scalability.

     

    Thursday, February 28, 2008 12:33 AM

All replies

  • HI Tyagi,

    It's likely an issue with the PAS cache taking that ten minutes to be invalidated following the cube processing.  If you need the most up to the minute information from the cube, it is possible to disable the cache entirely at the PAS layer, but you may notice a performance hit.  Caching can be disabled in the PAS global.asa, which is located by default at $\Inetpub\wwwroot\PAS.

     

    "...there are several settings in the Global.asa file that controls how the PAS Cache Engine works for each installation.  All of the defaults have been set at levels where the broadest performance level can be maintained, but in different installations these settings may need to be changed to increase performance and change some behavior.  Below is a list of each setting, what it does, and the applicable values.  Please note that these are the available settings for Cache Engine, and were based on the n 6.3 version of PAS.

     

    AutoInvalidateTime – This is the amount of time it takes for a cache entry in the cache to be flagged as ‘Invalid’.  By default this is set to 600 seconds or 10 minutes.

     

    Cache.LeasePeriod – This setting is used to flag each cache entry in the engine for the amount of time they may be used before they are automatically removed.  By default this setting is set to 21,600 or 6 hours.  Whenever a cache entry is re-used this timer is reset.

     

    Cache.SpaceLimitMB – This is the amount of hard drive space the cache entries can take up before the oldest entries begin to be ‘Invalidated’.  This is sometimes called the ‘Soft Limit’ since even though the files are invalidated; they still reside on the hard drive.  By default this setting is 512mb.

     

    Cache.HardSpaceLimitMB – This is the amount of hard drive space entries can take up before they are purged from the HD.  The oldest invalidated entries are purged first and then so on and so forth.  By default this is set to 1024mb.

     

    Cache.RelativeDirectory – The physical file directory where the main ‘cache’ folder is located.

     

    Cache.QualifiedDirectory – This is the directory string used by certain parts of the PAS code.  Notice that the application variable, “QueryPath” is used to help create the string.

     

    Cache.EvictionThreadTimeIntervalMS - This setting determines how often the thread to clean up the PAS entries is run.  By default this is set to 30000ms.

     

    Cache.HitRate = Sets the target hit rate of the cache engine. By setting to zero, effectively turns the cache engine off.  This setting was initially put into the system as a developer troubleshooting setting, but was left in to facilitate the ability to turn the Cache Engine off.

     

    Cache.StatsInitializationFile - The StatsInitializationFile property returns/sets the name of the file which initializes the statistics gathering. By default, this file is ...\Inetpub\wwwroot\PAS\CacheEngineStatsSetup.xml."

     

     

    Hopefully this helps you achieve the desired behavior.

     

    -Bob

     

    Wednesday, February 27, 2008 6:18 PM
  • Some have also chosen to deal with this as part of their SSIS package.  That is, they run the task to process the cube, and then run a task to clear the PAS cache.  Check out this post for a code sample of what the console app used in that task might look like.

     

    If you are doing things manually, you can just open the PAS Admin Tool, right-click, and choose to clear cache.

     

    You do have the ability to disable the PAS cache in the global.asa file in the PAS directory, but we recommend this only for troubleshooting, as doing this permanently will likely severely impact your performance and scalability.

     

    Thursday, February 28, 2008 12:33 AM
  •  

    thank you guys for the options, I´ll stick with the cache clean command, i think that will do it, but it was really good to get to know all those parameters in the global.asa file

     

    thank you again!

     

    cheers!

    Thursday, February 28, 2008 8:33 PM