Daniel Milroy

> so caching the result even if it is only valid for a second makes sense to me here. Probably 2s response time for the RPC is reasonable, however, if...

I could put together a PR with the caching and optimizations I performed so far pretty quickly. Assembling graph deltas and moving the resource-status RPC out of Fluxion would have...

> it would not be necessary AFAICT to keep actual graph data up to date with deltas, but only a representaiton in Rv1. I think a lot in terms of...

Even when I enable caching of all three outputs (`all`, `down`, and `alloc`) there is a considerable overhead from `flux resource list` beyond just the RPC. Setting the `R alloc`...

@grondo I forgot to highlight the considerable additional overhead involved in `flux resource list` I reported above during the group meeting yesterday and wanted to make sure you'd seen it.

I've got some time to work on this in Fluxion and will try to get a WIP PR out with support in the traverser, module, planners/pruning filter, and reader soon....

> It was prototyped in https://github.com/flux-framework/flux-core/pull/5818 but I only tested with sched-simple since I knew Fluxion would not handle it. Ok, I wasn't sure if multiple `free` responses with _R_...