3 ms·
Superinteresting and timely for us. Curious to plugin to our stack and see how it plays with our GPU visuals! I'm especially optimistic b/c the pydata bindings.
by lmeyerov 6y ago
Superinteresting and timely for us. Curious to plugin to our stack and see how it plays with our GPU visuals! I'm especially optimistic b/c the pydata bindings.
Can you share a bit more about k8s-less design plan + timeline? (apt/conda/docker/...?)
And any intuition for something like efficient Arrow/Parquet dataframe ingest/export? We're especially focused on Dask interop.
- sighingnow 6y agoThanks for you interests on GraphScope! We do have a concrete plan for k8s-less deployment and we already have an issue [1] to track that. That will be available before the end of March 2021. To simplify the environment setup process we will release a docker image for end-users, but without docker will be ok as well (requires building from sources). GraphScope use vineyard [2] as the storage layer for im-memory graph data structures. And current the graph type (aka. ArrowPropertyFragment in GraphScope) uses a set of arrow tables and arrays under the hood. GraphScope supports a `to_vineyard_dataframe` method on the computation context [3]. We also has a plan for integration between vineyard and dask (may could be delivered in March as well). At that time the interop between dask would be straightforward. [1]: https://github.com/alibaba/GraphScope/discussions/113 https://github.com/alibaba/GraphScope/discussions/113 [2]: https://github.com/alibaba/libvineyard https://github.com/alibaba/libvineyard [3]: https://graphscope.io/docs/reference/context.html#graphscope.framework.context.BaseContext.to_vineyard_dataframe https://graphscope.io/docs/reference/context.html#graphscope...