daikaginza e60cbb42e3 perf(terrain): evict from the front of the point cache instead of sorting it ...

Once the cache was full, every write sorted all 50,000 entries to find the
oldest. A Map keeps insertion order, so keep the map in fetch-time order
and delete from the front: the resolver re-inserts each point it refetches
(an overwrite would leave it in its old place), and the disk load sorts
once, since a file written before this change, or a migrated raw-batch
cache, is not in age order.

Suggested by asturksever on #975.

2026-10-23 11:57:37 +07:00

..

mcp

fix(mcp): serialize shared panel key repair and credit report

2026-10-07 15:12:44 -07:00

providers

perf(terrain): evict from the front of the point cache instead of sorting it

2026-10-23 11:57:37 +07:00

standalone

refactor(voice): isolate gemini live provider core

2026-10-19 21:40:40 +05:30