The post discusses a case study from Aladdin Wealth Tech, detailing how they identified and fixed a performance issue with a Java hash table handling very large portfolios in an Apache Spark job. It was discovered that hash collisions in the Apache Commons Lang3 Pair class were causing quadratic time complexity (O(N2)). By

11m read timeFrom engineering.blackrock.com
Post cover image
Table of contents
Solving the Mystery of the Slow Hash TableVery Large PortfoliosJMH BenchmarkPosition ContributorsHash Table BasicsHash CollisionThe FixLessons learned

Sort: