openmw

Commit Graph

Author	SHA1	Message	Date
Evil Eye	77d554594f	Add ReadersCache::clear	8 months ago
clang-format-bot	ddb0522bbf	Apply clang-format to code base	2 years ago
elsid	3affe9913f	Limit the number of simultaneously open not actively used content files Use LRU cache for ESMReaders. When cache capacity is reached close least recently used ESMReader. Remember the file name if a reader was open. Once the reader requested again open the file if there is stored name for it. Put released ESMReader to the back of the free items list. Close ESMReader's from the front of the free items list. Cached item can be used only by one client at the same time. If the same item is requested twice exception is thrown. This should never happen in practice. If this happens need to fix the client logic. It's allowed to go over the capacity limit when requesting different readers. Ideally this should never happen but there will be system error anyway signalizing about too many open files. Need to fix client logic in this case. All places that were using a vector of ESMReaders now using the cache. Cache is local for each use case and there is no need for a thread safety.	3 years ago

Author

SHA1

Message

Date

Evil Eye

77d554594f

Add ReadersCache::clear

clang-format-bot

ddb0522bbf

Apply clang-format to code base

elsid

3affe9913f

Limit the number of simultaneously open not actively used content files

Use LRU cache for ESMReaders. When cache capacity is reached close least
recently used ESMReader. Remember the file name if a reader was open. Once the
reader requested again open the file if there is stored name for it. Put
released ESMReader to the back of the free items list. Close ESMReader's from
the front of the free items list.

Cached item can be used only by one client at the same time. If the same item is
requested twice exception is thrown. This should never happen in practice. If
this happens need to fix the client logic.

It's allowed to go over the capacity limit when requesting different readers.
Ideally this should never happen but there will be system error anyway
signalizing about too many open files. Need to fix client logic in this case.

All places that were using a vector of ESMReaders now using the cache. Cache is
local for each use case and there is no need for a thread safety.

3 Commits (96845081c03ed0bfd7effa86273ddb2ce74ece5b)