- 
    Enhancement 
- 
    Resolution: Fixed
- 
     P4 P4
- 
    17, 20, 21
- 
        b24
                    One of our services has a hot path with AES/GCM cipher reuse. The JDK code reinitializes the session key on that path, and JDK-8308105 shows up prominently there. Fixing JDK-8308105 would take a while, as would likely require multiple patches in VM internals. Meanwhile, we can avoid the multiarray allocations in AESCrypt.makeSessionKey completely, reaping performance benefits.
            
- relates to
- 
                    JDK-7185471 Avoid key expansion when AES cipher is re-init w/ the same key -           
- Closed
 
-         
- 
                    JDK-8308105 Multi-array allocations are very slow -           
- Open
 
-         
- 
                    JDK-8347606 Optimize Java implementation of ML-DSA -           
- Resolved
 
-         
- 
                    JDK-8347608 Optimize Java implementation of ML-KEM -           
- Resolved
 
-         
             (1 links to)
        
    
 
        