17 ms·

Super glad to hear that! What are some things you're missing on the client/server streaming? I'm aware that there is much to do but would love to hear your spe

by nikonp 2y ago

Super glad to hear that! What are some things you're missing on the client/server streaming? I'm aware that there is much to do but would love to hear your specific issues

upbeat_general 2y ago
Honestly most of the things I would like food are very oriented toward research/sharing use-cases, which I realize that is distinct from a lot of your users, but can mean: - Working with large remote datasets/clusters - Needing to share visualizations with others [both interactive, and pre-recorded/controlled] - Being able to easy switch between N runs to look at data/results over time Concretely: - Currently it seems you need to forward multiple ports, and for each new session you need to re-connect. My memory is foggy but I found it was a lot of hassle to just connect a thin-desktop client to a remote backend. - The support for baked-html is great, but it has limits (namely I was hitting some size limitations) and it would be cool to have a server that can read rr files from disk and stream them on-demand [e.g., point to a directory and let the user select] - Generally speaking, I found the workflow difficult to integrate to the typical ML setup. Obviously not a priority for rerun but I think a little improvement [like the point above] could help a lot. - A built-in screen recording feature would be great. I spent a lot of time screen recording and re-sharing clips. Again, these are mainly nitpicks, love the tool overall and have recommended it to several people.
- nikonp 2y ago
  Thanks a lot I really appreciate you writing this out! I'd say most of your requests are things we'd like to address in the future. Built in screen recording is a common request and something I think makes sense for the open source project. A lot of the other requests require a central service of some kind to achieve high performance and/or a smooth user experience so those fall into the bucket of what will go into our commercial offering.

by nikonp 2y ago

Super glad to hear that! What are some things you're missing on the client/server streaming? I'm aware that there is much to do but would love to hear your specific issues

upbeat_general 2y ago

Honestly most of the things I would like food are very oriented toward research/sharing use-cases, which I realize that is distinct from a lot of your users, but can mean: - Working with large remote datasets/clusters - Needing to share visualizations with others [both interactive, and pre-recorded/controlled] - Being able to easy switch between N runs to look at data/results over time Concretely: - Currently it seems you need to forward multiple ports, and for each new session you need to re-connect. My memory is foggy but I found it was a lot of hassle to just connect a thin-desktop client to a remote backend. - The support for baked-html is great, but it has limits (namely I was hitting some size limitations) and it would be cool to have a server that can read rr files from disk and stream them on-demand [e.g., point to a directory and let the user select] - Generally speaking, I found the workflow difficult to integrate to the typical ML setup. Obviously not a priority for rerun but I think a little improvement [like the point above] could help a lot. - A built-in screen recording feature would be great. I spent a lot of time screen recording and re-sharing clips. Again, these are mainly nitpicks, love the tool overall and have recommended it to several people.

nikonp 2y ago
Thanks a lot I really appreciate you writing this out! I'd say most of your requests are things we'd like to address in the future. Built in screen recording is a common request and something I think makes sense for the open source project. A lot of the other requests require a central service of some kind to achieve high performance and/or a smooth user experience so those fall into the bucket of what will go into our commercial offering.