tree 83367308fcc0a2ee0c62363a1adf428eddeaac9e
parent 06256d6690a8b2f7f2b7b71baccbedd942f4e5be
author Prudhvi Akhil Alahari <prudhvi.alahari@linaro.org> 1676882574 +0530
committer Prudhvi Akhil Alahari <prudhvi.alahari@linaro.org> 1677607061 +0000

Don't limit PerThreadCache rather limit PerThreadProjectCache

Before this change, PerThreadCache has an enforcing limit of 25. The
main reason for having a limit was to restrict the number of projects
cached per thread to avoid OOM exceptions (Ic2f6e11719). By enforcing
a limit on the whole PerThreadCache for just projects use case is
effecting other use cases (such as PerThreadRefByNameCache in
I7de4e2183) of PerThreadCache.

Having a limit for number of projects stored in PerThreadCache is
needed. But as PerThreadCache is designed to be generic, that limit
must be applied to just projects use case, not the whole PerThreadCache.

Introduce PerThreadProjectCache which enforces the limit instead of
PerThreadCache. Update tests accordingly.

PerThreadCache is needed in creating a per-request ref cache using
a snapshot of RefDirectory in I174fbfdb95. This change makes it
possible to create a per-request ref cache.

Also, code-owners plugin uses PerThreadCache in a couple of places.
As one of the usage is projects specific, update code-owners plugin
to use PerThreadProjectCache post this change.

Release-Notes: skip
Change-Id: I1090446b6555296c64da1c01db39b7ac3dc6f2a3