Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dask dataframe chunksize/partioning affects line aggregation #464

Open
philippjfr opened this issue Sep 18, 2017 · 0 comments
Open

Dask dataframe chunksize/partioning affects line aggregation #464

philippjfr opened this issue Sep 18, 2017 · 0 comments
Labels

Comments

@philippjfr
Copy link
Member

philippjfr commented Sep 18, 2017

When using a dask dataframe during line aggregation the chunksize affects the result, this is likely because different chunks aren't processed together effectively splitting the path. In this example I create dask dataframes with varying chunksizes and visualize the effect:

%%opts Image [aspect='square' xaxis=None yaxis=None sublabel_format=''] Layout [hspace=0.1 vspace=0.1]
import dask.dataframe as dd
from holoviews.operation.datashader import datashade, aggregate
paths = hv.Path([[(i+x, i*10) for i in range(10)] for x in range(10)])
hv.Layout([aggregate(hv.Curve(dd.from_pandas(paths.dframe(), chunksize=p)),
                    dynamic=False, width=10, height=10).relabel('Chunksize: %d' % p)
           for p in range(1, 11)])

image

You can see that basically every chunksize or number of partitions produces a slightly different result.

@philippjfr philippjfr changed the title Dask dataframe chunksize affects line aggregation Dask dataframe chunksize/partioning affects line aggregation Sep 18, 2017
@philippjfr philippjfr added the bug label Sep 18, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant