Uploaded image for project: 'Infinispan'
  1. Infinispan
  2. ISPN-663

Eviction with passivation using JdbmCacheStore is 100 times slower in 4.1 vs 4.0

    XMLWordPrintable

Details

    • Hide

      Run Test provided against 4.1.0.FINAL and 4.0.0.FINAL etc

      Show
      Run Test provided against 4.1.0.FINAL and 4.0.0.FINAL etc

    Description

      Eviction with passivation enabled using the JdbmCacheStore appears to be significantly slower in 4.1.0.FINAL vs 4.0.0.FINAL.

      The degredation in performance is so signficant to make it impossible to use

      The performance issue seems to due as the JdbmCacheStore synching the filesystem via FileDescriptor.sync() or similar which occurs during every object passivation and each passivation occurs as a new object is added beyond the EvictionMaxEntries capacity.

      The attached test inserts 1000 values into two caches

      Both caches use a JdbmCacheStore and LRU

      PASSIVATIONLRU10 runs with cache with EvictionMaxEntries 10
      PASSIVATIONLRU1000 runs with cache with EvictionMaxEntries 1000

      4.1.0.FINAL

      PASSIVATIONLRU10 Time Taken : 51704
      PASSIVATIONLRU1000 Time Taken : 4484

      4.0.0.FINAL
      PASSIVATIONLRU10 Time Taken : 281
      PASSIVATIONLRU1000 Time Taken : 141

      4.2.0.ALPHA2
      PASSIVATIONLRU10 Time Taken : 51047
      PASSIVATIONLRU1000 Time Taken : 5156

      Attachments

        Issue Links

          is blocked by

          Bug - A problem that impairs or prevents the functions of the product. ISPN-717 Trying to modify an entry that is not loaded into memory triggers an unnecessary CacheStore.load() operation.

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) ISPN-328 Async store to support frequency based flushing

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • To Do

          Activity

            People

              trustin_jira Trustin Lee (Inactive)
              paulnardone Paul Nardone (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: