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

Optimize EncoderCache async methods that are usually completed synchronously

This issue belongs to an archived project. You can view it, but you can't modify it. Learn more

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: Major Major
    • 15.0.0.Final
    • None
    • None
    • None

      Some EncoderCache methods that are normally completed asynchronously create additional CompletableFuture objects. For example getAsync always applies a thenApply method which involves always creating a new CompletableFuture as well as some internal allocations (the inner ones are usually optimized away).

      We can instead check for the stage being complete and then compare the unwrapped value with the final value to see if we even need to create a new CompletableFuture object.

              wburns@redhat.com Will Burns
              wburns@redhat.com Will Burns
              Archiver:
              rhn-support-adongare Amol Dongare

                Created:
                Updated:
                Resolved:
                Archived: