3 ms·
Totally agree. And it turns out not caused by the layout algorithm but exactly the rendering. We've been drawing on canvas without proper acceleration for too
by v-yadli 9y ago
Totally agree. And it turns out not caused by the layout algorithm but exactly the rendering.
We've been drawing on canvas without proper acceleration for too long.
- lmeyerov 9y agoFor more scalable on both, generally happy to share Graphistry API keys -- ping pygraphistry@graphistry.com . At the 100K+ scale, you need to optimize both :) I'm excited to see both Stardust and the related DeckGL project. We've internally built several related framework layers (ex: streaming for cloud GPU offloading), and picking accessible abstractions for different developer personas is hard. Stardust & DeckGL are both (potentially) enabling dedicated visualization engineers to work more closely with high performance computing engineers. That's impressive: we deferred that problem to focus energy on enabling embedding for regular web developers (which goes above stardust) and scaling to the next 1000X (which goes below/adjacent)... but at the expense of making it harder for non-webgl visualization engineers to work on parts of our stack. Long-term, I think their mindset is right, so, I've definitely been enjoying these projects!