LUMIERA.clone/tests/vault
Ichthyostega 5fafb16807 BufferProvider: decide to use only a simple heuristics for reservation
At the begin of each Render Node `pull()`, the render job is expected
to ''announce'' a maximum expected allocation requirement to the `BufferProvider`,
which information is passed-on to the `LocalMemPool` to determine
to which degree it can be satisfied with allocations from that local pool.

Without actual empiric observation, it is impossible to determine
the relevance of this step, how it should be resolved heuristically
against the known contents of the pool, and how much effort to spend
on that step.

Thus I'll settle for the ''simplest thing that can possibly work'' —
which is to check only for close matches and rather rely on additional
allocations, forwarded asynchronously, assuming that the clean-up
heuristics will deal with excess allocations quickly.
2026-04-27 00:25:10 +02:00
..
cache BufferProvider: relocate TestFrame and dummy-hash computations 2026-03-07 23:02:35 +01:00
gear Library: investigate design for an opaque inline functor 2026-04-08 01:53:53 +02:00
io BufferProvider: relocate TestFrame and dummy-hash computations 2026-03-07 23:02:35 +01:00
mem BufferProvider: decide to use only a simple heuristics for reservation 2026-04-27 00:25:10 +02:00
out BufferProvider: complete the clean-up effort 2026-04-14 01:22:55 +02:00
storage BufferProvider: relocate TestFrame and dummy-hash computations 2026-03-07 23:02:35 +01:00
toolkit BufferProvider: relocate TestFrame and dummy-hash computations 2026-03-07 23:02:35 +01:00
DIR_INFO Scheduler: investigate modes of operation 2023-07-03 18:40:37 +02:00