gitea

Commit Graph

Author	SHA1	Message	Date
6543	00a981d341	Update go-chi/cache to utilize Ping() (#19719 ) * update gitea.com/go-chi/cache -> v0.2.0 * ajust to new interface * refactor	3 years ago
Lunny Xiao	9f31f3aa8a	Add an abstract json layout to make it's easier to change json library (#16528 ) * Add an abstract json layout to make it's easier to change json library * Fix import * Fix import sequence * Fix blank lines * Fix blank lines	4 years ago
zeripath	2f725cbc9e	Add LRU mem cache implementation (#16226 ) The current default memory cache implementation is unbounded in size and number of objects cached. This is hardly ideal. This PR proposes creating a TwoQueue LRU cache as the underlying cache for Gitea. The cache is limited by the number of objects stored in the cache (rather than size) for simplicity. The default number of objects is 50000 - which is perhaps too small as most of our objects cached are going to be much less than 1kB. It may be worth considering using a different LRU implementation that actively limits sizes or avoids GC - however, this is just a beginning implementation. Signed-off-by: Andrew Thornton <art27@cantab.net>	4 years ago

Author

SHA1

Message

Date

6543

00a981d341

Update go-chi/cache to utilize Ping() (#19719 )

* update gitea.com/go-chi/cache -> v0.2.0

* ajust to new interface

* refactor

Lunny Xiao

9f31f3aa8a

Add an abstract json layout to make it's easier to change json library (#16528 )

* Add an abstract json layout to make it's easier to change json library

* Fix import

* Fix import sequence

* Fix blank lines

* Fix blank lines

zeripath

2f725cbc9e

Add LRU mem cache implementation (#16226 )

The current default memory cache implementation is unbounded in size and number of
objects cached. This is hardly ideal.

This PR proposes creating a TwoQueue LRU cache as the underlying cache for Gitea.
The cache is limited by the number of objects stored in the cache (rather than size)
for simplicity. The default number of objects is 50000 - which is perhaps too small
as most of our objects cached are going to be much less than 1kB.

It may be worth considering using a different LRU implementation that actively limits
sizes or avoids GC - however, this is just a beginning implementation.

Signed-off-by: Andrew Thornton <art27@cantab.net>

3 Commits (9f3906b2a3ab410bfb16aa1b69484554b0601e5c)