Skip to content

Bump AsyncKeyedLock to 8.0.2, clean up lock.#12

Open
MarkCiliaVincenti wants to merge 3 commits intoNotOfficer:masterfrom
MarkCiliaVincenti:dep
Open

Bump AsyncKeyedLock to 8.0.2, clean up lock.#12
MarkCiliaVincenti wants to merge 3 commits intoNotOfficer:masterfrom
MarkCiliaVincenti:dep

Conversation

@MarkCiliaVincenti
Copy link
Copy Markdown
Contributor

I also wanted to comment on how the locker options may be suboptimal, especially that PoolInitialFill value. 64 means you are sure you will have a minimum of 64 concurrent threads with distinct FGuid values, so you want to create them immediately on startup so they're already allocated.

The standard settings I like working with (also set as the default values) are 20 for the pool size and 1 for the pool initial fill. Please note that the 20 doesn't mean a hard rate limit of 20 concurrent threads. If a 21st one comes along, the pool would be empty and a SemaphoreSlim object is created just as if there was no pooling involved.

@MarkCiliaVincenti MarkCiliaVincenti changed the title Bump AsyncKeyedLock to 7.1.8, clean up lock. Bump AsyncKeyedLock to 8.0.0, clean up lock. Jan 2, 2026
Updated AsyncKeyedLock package version from 8.0.0 to 8.0.2.
@MarkCiliaVincenti MarkCiliaVincenti changed the title Bump AsyncKeyedLock to 8.0.0, clean up lock. Bump AsyncKeyedLock to 8.0.2, clean up lock. Feb 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant