You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
See individual README files for complete algorithm lists and usage examples.
161
-
162
-
## Performance Characteristics
163
-
164
-
### Vermeer (In-Memory)
165
-
166
-
-**Throughput**: Optimized for fast iteration on medium-sized graphs (millions of vertices/edges)
167
-
-**Latency**: Sub-second query response via REST API
168
-
-**Memory**: Requires graph to fit in total worker memory
169
-
-**Scalability**: Horizontal scaling by adding worker nodes
193
+
> **Computer (Java) Algorithms**: For Computer's 45+ algorithm implementations including distributed Triangle Count, Rings detection, and custom algorithm development framework, see [Computer Algorithm List](./computer/README.md#available-algorithms).
170
194
171
-
### Computer (Distributed BSP)
195
+
##When to Use Which
172
196
173
-
-**Throughput**: Handles billions of vertices/edges via distributed processing
174
-
-**Latency**: Batch-oriented with superstep barriers
175
-
-**Memory**: Auto spill to disk when memory is insufficient
176
-
-**Scalability**: Elastic scaling on K8s with pod autoscaling
197
+
### Choose Vermeer when:
177
198
178
-
## Use Cases
199
+
- ✅ Quick prototyping and experimentation
200
+
- ✅ Interactive analytics with built-in Web UI
201
+
- ✅ Graphs up to hundreds of millions of edges
202
+
- ✅ REST API integration requirements
203
+
- ✅ Single machine or small cluster with high-memory nodes
204
+
- ✅ Sub-second query response requirements
179
205
180
-
### When to Use Vermeer
206
+
**Performance**: Optimized for fast iteration on medium-sized graphs with in-memory processing. Horizontal scaling by adding worker nodes.
181
207
182
-
- Quick prototyping and experimentation
183
-
- Interactive graph analytics with Web UI
184
-
- Medium-scale graphs (up to hundreds of millions of edges)
185
-
- Single-machine or small cluster deployments
186
-
- REST API integration requirements
208
+
### Choose Computer when:
187
209
188
-
### When to Use Computer
210
+
- ✅ Billions of vertices/edges requiring distributed processing
211
+
- ✅ Existing Kubernetes or YARN infrastructure
212
+
- ✅ Custom algorithm development with Java
213
+
- ✅ Memory-constrained environments (auto disk spill)
214
+
- ✅ Integration with Hadoop ecosystem
189
215
190
-
- Large-scale batch processing (billions of vertices)
191
-
- Existing Kubernetes or YARN infrastructure
192
-
- Custom algorithm development with Java
193
-
- Memory-constrained environments (auto spill to disk)
194
-
- Integration with Hadoop ecosystem
216
+
**Performance**: Handles massive graphs via distributed BSP framework. Batch-oriented with superstep barriers. Elastic scaling on K8s.
0 commit comments