This channel is rarely used. For other channels to contact the dask community, please see https://docs.dask.org/en/stable/support.html
I guess it shouldn't be too hard to kick off dask-jobs from within Flask. Was just wondering whether there are any examples and experiences doing that around.
Not having to setup message queues and the like seems like a huge plus to me.
but thanks for the documentation link
it looks like all these methods target optimal use of data that has been localized to the cluster using e.g.
scatter, is that right?
in my use case, there's no explicit management of data on the cluster -- I just locally define a dask array and try to compute its first element (for example) using the distributed scheduler
Yes, about manully moving things around in cluster memory. https://distributed.dask.org/en/latest/work-stealing.html describes when Dask might do this automatically
You should isolate the exact code, expectations and findings in an issue, then
hello everyone, I have question. I'm trying to run computation that would require large dataset as argument. Something like df.apply(navigate_over_array, args=(very_big_array,)). I'd like to pre-scatter very_big_array to all workers so function can reference it there. What's good way to pass it? If I scatter, I get future, is there a way that would allow me to access data behind this future from applied function in worker?
or is there better way to achieve this result?
I'm configuring Dask on a single node together with a JupyterHub instance. I would like to specify a default LocalCluster when people create one. I found the distributed.yaml in /etc/dask. Can I specify stuff like n_workers, threads_per_worker anywhere there? I've been looking for a complete list of configuration options, but I'm unable to find it
You should be able to find the relevant parts of the graphical output quite easily. It ought to be possible to make aggregate graphics (like the memory and processing sections on the status/ dashboard) or just refuse to work with datasets that have become too large, or even to monitor internal memory usage of the dashboard and halt when it gets too big.
(as I've just done myself :D)
ended up commenting here https://github.com/dask/distributed/issues/2979#issuecomment-530915742
It is, of course, in a separate thread, as opposed to separate process, so it will always be a little tricky to know when some memory limit is approached because of the graphics; however, I can imagine safety safeguards which turn off some graphics known to be resource-hungry above some threshold
Hi all, I'm pretty new to Dask and just had a quick question I was wondering if anyone could help me with - I have two 3D dask arrays and want to broadcast the
solve operation across the last 2 dimensions, i.e. given A and B I want to do C[i,:,:]=solve(A[i,:,:], B[i,:,:]) for all i in the leading dimension... I tried the below but it seems to be really slow (slower than numpy) - does anyone know what I'm doing wrong/what I could do better? Sorry if this was the wrong place to ask.C = da.apply_gufunc(np.linalg.solve, "(i,j),(i,k)->(j,k)", A, B, vectorize=True,output_dtypes=A.dtype)
Does it just set
scale and then read it back then scale up/down from that?
@mrocklin Do you think a maximum limit of workers which can be used by a submitted job would be useful, Although I see that we already have a param for providing a set of workers.
On a broader idea worker pools, something like this could be rather useful.
Can these two behaviours be achieved currently?
I think there's a few books people have written on using dask, but AFAIK none of the authors are affiliated with the project. We generally recommend people walk through the documentation. There are also a few tutorials around, this is the one we usually give: https://github.com/dask/dask-tutorial
specifically, I often find myself trying to apply an arbitrary function on chunks of an array, but the output of that function is not an array (image registration is usually where this comes up for me, second most common is trying debug chunked operations, e.g.
map_blocks(func_that_returns_a_debug_string))
but
map_blocks assumes that I'm mapping an array on to another array, which doesn't match these use cases well