RFR: 8315559: Delay TempSymbol cleanup to avoid symbol table churn [v10]

[Oli Gillespie]

On Tue, 28 Nov 2023 13:07:03 GMT, Coleen Phillimore <coleenp at openjdk.org> wrote:

>> Yes, there is one additional test for the draining but it's quite simple. The drain feature actually helps with the other tests, that's how we can avoid the queue interfering with ref counts for the tests (create temp symbol, immediately drain queue), so even if we don't drain periodically I'd still leave the feature there for the existing tests.
>> 
>> What about the fact that not draining the queue means we could keep 128 symbols alive indefinitely? Are you not concerned because that's a small amount, and/or because natural churn will likely keep the queue moving?
>
> I think the footprint savings is probably negligible.  I like the idea that the queue is periodically drained because it might show issues where we've messed up the refcounts, but they'd be hard to debug, so maybe not worth it. So I see neither the harm nor the benefit of draining the queue in the periodic task, but we should have the feature for the one test.

I've removed drain from the concurrent cleanup. I left it public and tested, is that reasonable or do you prefer I make it private somehow (not sure the typical way to have test-only methods)?

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

PR Review Comment: https://git.openjdk.org/jdk/pull/16398#discussion_r1407844595