TF 753 or 757 ASE 16

Hello,

ASE 16 SP02 PL03 on RHEL 7.2

In order to reduce or get rid of the message "Spinlock Resource->rproccache_spin at address...", "Procedure Cache Spinlock (Resource->rproccache_spin)", ect

which TF should be used : TF 753 or TF 757 ?

I was checking https://wiki.scn.sap.com/wiki/display/SYBASE/Spinlocks+and+CPU+usage+in+SAP+ASE#

and I was just thinking which one it would be best.. or both ?

Thank you

Jose

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • Best Answer
    Nov 24, 2016 at 04:57 PM

    See the following for discussions re: procedure cache (spinlocks), ELC and TFs 753/757:

    ASE Procedure Cache and Engine Local Cache (ELC)

    Get Rid of the Crutches – Right Size Proc Cache

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Nov 24, 2016 at 05:59 PM

    I think TF753 has been superseded by the config setting

    "enable large chunk elc" in Sybase 16

    We have it set to 0 - although I'm told Sybase 16 works better than Sybase 15.7 with large chunk elc.

    However, we haven't tried it so can't comment how well it works.

    Add comment
    10|10000 characters needed characters exceeded

  • Nov 24, 2016 at 07:06 PM

    Thank you guys,

    But still wondering:

    -Is TF 757 is similar to TF753 ?[( if any one has the specifics on 757 it'll be great)

    -According to "ASE Procedure Cache and Engine Local Cache (ELC)"

    large allocation auto tune (replaces traceflag 753) -> we have set it to 0 for a while, but we are still getting this message followed by a stack trace:

    "Spinlock Resource->rproccache_spin at address..."

    then ,It's advisable to use 753 and eventually increase Proc cache ?

    -Does TF 757 has been replaced by a new ASE parameter ?

    Regards

    Jose

    Add comment
    10|10000 characters needed characters exceeded

    • Hi Jose,

      Keep in mind, the association with any of these trace flags and configurations have no bearing on whether or not normal processing requires rproccache_spin spinlock. These configurations change usage of the caches not the necessity of the spinlock when it is being used.

      Asking how to get rid of "Spinlock Resource" issues during a stacktrace, is answered by getting rid of the stack trace. Spinlocks will be held anytime a protected memory address needs to be accessed. As long as there are multiple engines, multiple users competing for the same memory, you will have grabs as well as spins/waits for the spinlock.

Skip to Content