Skip to content

Commit 192848c

Browse files
committed
updated intro
1 parent 61d9ec3 commit 192848c

File tree

1 file changed

+0
-17
lines changed

1 file changed

+0
-17
lines changed

docs/source/cugraph_intro.md

Lines changed: 0 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -48,23 +48,6 @@ high-speed ETL, statistics, and machine learning. To make things even better,
4848
RAPIDS and DASK allows cuGraph to scale to multiple GPUs to support
4949
multi-billion edge graphs.
5050

51-
Every release of RAPIDS is accompanied with one or more wonderful BLOG(s)
52-
about the features of that release (for example, see the release 0.8 blog [1]
53-
or Life after Hadoop). This article is slightly different. While current
54-
features will be discussed, the main focus is on presenting the vision of
55-
cuGraph and how we envision users will interact with the libraries. The cuGraph
56-
team has been working hard to provide a rich set of initial features. Over the
57-
past three releases (RAPIDS release 0.6 was the first to include cuGraph), the
58-
team has provided over a dozen algorithms. The initial goal was to simply get
59-
graph analytics released and available with a familiar NetworkX-like API. That
60-
is great in the short term since it allows an easy path to switch to RAPIDS.
61-
However, cuGraph development will slowly shift towards improving ease-of-use,
62-
interoperability, and integration with the rest of RAPIDS. That is not an easy
63-
task since there is still so much to be added to the cuGraph ecosystem. Don’t
64-
worry, the goal of getting new analytics out will continue since there is a very
65-
long list of algorithms to release.
66-
67-
6851

6952
# Terminology
7053

0 commit comments

Comments
 (0)