Fixed
Details
Assignee
Zac SpitzerZac SpitzerReporter
Zac SpitzerZac SpitzerPriority
NewLabels
Fix versions
New Issue warning screen
Before you create a new Issue, please post to the mailing list first https://dev.lucee.org
Once the issue has been verified, one of the Lucee team will ask you to file an issue
Sprint
None
Details
Details
Assignee
Zac Spitzer
Zac SpitzerReporter
Zac Spitzer
Zac SpitzerPriority
Labels
Fix versions
New Issue warning screen
Before you create a new Issue, please post to the mailing list first https://dev.lucee.org
Once the issue has been verified, one of the Lucee team will ask you to file an issue
Sprint
None
Created 6 November 2024 at 17:54
Updated 6 January 2025 at 17:06
Resolved 6 January 2025 at 17:06
I noticed there was a lot of hashmap resizing going on running thread tests
https://github.com/lucee/Lucee/blob/6.2/core/src/main/java/lucee/runtime/net/http/HttpUtil.java#L59
due to the request scope having a lot of items (1030) from various tests including
LDEV-947: cfsavecontent & cfinclude - java.util.ConcurrentModificationExceptionDeployed
which added 1000 items to the request scope, which i cleaned up, but it also made the request scope synchronized
https://github.com/lucee/Lucee/commit/570dd85a31fded78afd8e9ff549704fdc3c90820
but due to the initial size being 32 items, the resizing of the hash is being done synchronized
just cleaning up that scope between tests made the test suite run 50s faster
this doesn’t need to be syncronized
the initial capacity for the cloned request scopes should be large enough to fit all the items