Open RaitoBezarius opened 4 months ago
Meta comment: Ideally, we can get members of the community involved in the design and development of this service. And then have a good hand-over to the infra team for deployment. I don't know how well the infra team can scale if they also become responsible for R&D.
Meta comment: Ideally, we can get members of the community involved in the design and development of this service. And then have a good hand-over to the infra team for deployment. I don't know how well the infra team can scale if they also become responsible for R&D.
I agree, as I mention it, I developed similar stuff (linked in the body of the original issue) and I can develop a specialized tool for it, but it would make sense to reuse Hydra evaluation results for that and pass them on to the right tool. Because of that, it seems hard to me to put such an issue elsewhere than the infra issue tracker.
@tomberek you wanted to do something similar if I remember correctly our discussion at OceanSprint. I personally am also interested for research purposes.
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/when-should-meta-attributes-be-computed-vs-raw-data/42833/14
Is your feature request related to a problem? Please describe.
I am always frustrated whenever I build something that relies on listening to channel bumps and consuming evaluation results, I cannot find a single place where I could source them and would need to memoize them myself.
This is expensive on my weak web services.
Describe the solution you'd like
I would like an evaluation memoization service that could reuse Hydra evaluation results.
Something where I could:
(a) listen to new channel bumps (b) ask for any evaluation result for any channel bump
If it does exist, I would like documentation to rely on this and best practices.
Describe alternatives you've considered
Additional context