{"version":"2.1.300","anchor":"string-cache-switched-to-an-lru-with-size-cap","canonical_anchor":"string-cache-switched-to-an-lru-with-size-cap","heading":"Two text caches now have a size limit","tier":"internal","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/string-cache-switched-to-an-lru-with-size-cap","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### Two text caches now have a size limit\n\nTwo internal text caches now hold at most 8192 entries, and one also has a total size cap\n\n**What**\n\nA cache stores results so they do not have to be worked out again. Two caches, one for lowercasing and normalising text and one for a text parser, now drop the least recently used entries once full. Each holds at most 8192 entries, and one also has a total size cap of 4194304. Before, they were plain caches with no limit.\n\n**Why**\n\nThe memory these caches use can no longer keep growing over a long session.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}