RFR: 8349007: The jtreg test ResolvedMethodTableHash takes excessive time

[Coleen Phillimore]

On Wed, 2 Apr 2025 17:28:12 GMT, Coleen Phillimore <coleenp at openjdk.org> wrote:

> This is mostly test change.  ResolvedMethodTableHash.java is run /manual but still takes a long time and doesn't really verify that the hash code is any good.  This add logging, triggers concurrent work like other ConcurrentHashtables, and checks that a small table is not rehashed.
> Tested with tier1 (including test).

This test was never meant to be a stress test, it was just checking that the hashcode didn't result in collisions for methods with the same name and signature.
With my change it takes 32 seconds to run make test TEST=runtime/MemberName/ResolvedMethodTableHash.java which is probably about 31 seconds for jtreg to run.

-------------

PR Comment: https://git.openjdk.org/jdk/pull/24383#issuecomment-2776870921