1 Reply Latest reply on May 14, 2004 10:53 AM by gavinandrews

    Performance of commit-option D

    gavinandrews Newbie

      I thought I might move towards commit-option D (from my current default commit-option B)...

      I notice that after the cache has been invalidated <optiond-refresh-rate> is 120 the NEXT operation is VERY VERY slow. i.e. Between invalidations the performance is good but when the cache is empty after having been flushed there is a pause on the next ejbLoad

      Any ideas?

      Thanks,
      Gavin

      3.2.2RC4 + Sybase 12