Nick Becker
Nick Becker
> @beckernick So if I'm not mistaken, going to fit_transform should already solve a big part of the problem, right? If so, then this should be a quick fix. Nice!...
It looks like [our docs](https://docs.rapids.ai/api/cugraph/nightly/nx_cugraph/nx_cugraph/) are wrong (screenshot below). We [should be using](https://networkx.org/documentation/stable/reference/backends.html) `NETWORKX_CACHE_CONVERTED_GRAPHS` not `CACHE_CONVERTED_GRAPH` to configure caching behavior.
Thanks for reporting. Would you be able to give this a try with the stable v24.10 release that just came out? I'm not able to reproduce it in the current...
Closing, but please feel free to re-open if this reproduces in v24.10+
@cjnolet , do you expect this is as straighforward as adding a `graph_degree = max(graph_degree, n_neighbors)` for this codepath?
Thanks Corey. @saucechef , for now, you can do this manually on your side if you're using more neighbors than the default graph degree of 64 by using the `build_kwds`...
Seems like this would be an expansion of https://github.com/networkx/networkx/pull/6876
This discussion came up again today, as DBSCAN Python docs indicate it's possible to use Handles/streams for concurrency. We noted several points: - There wasn't a handy example of how...
@jrhemstad @harrism , is this still a relevant issue?
Sounds good. Wondering if perhaps I'm hitting some thread contention during IO? If I limit DuckDB to a single thread, I see similar performance. ```python import duckdb import chdb duckdb_con...