Commit 83f2a34
committed
docs: run the MySQL demo at 1,000,000 rows
Ten rows proved the pipeline worked but said nothing about whether it is
fast, which is the question a reader actually has. Reseeded the container
with 1,000,000 orders, 333,333 of them shipped, and measured:
1,932 ms end to end, MySQL wire to a DuckDB table
~518,000 source rows per second
Warm. First run after a cold start is 5.48 s, most of that the DuckDB
mysql extension loading, and a repeat run settles at ~1.96 s wall clock
from the Python process starting.
Correctness checked rather than assumed: 333,333 rows landed, and spot
values are right (13.03 * 0.8 = 10.42, label region-customer). Both
derived columns and the filter compiled to SQL and ran inside DuckDB, so
none of the million rows passed through Python. That is the claim the
number is there to support.1 parent 0c6fae7 commit 83f2a34
2 files changed
Lines changed: 44 additions & 35 deletions
Loading
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
227 | 227 | | |
228 | 228 | | |
229 | 229 | | |
230 | | - | |
231 | | - | |
| 230 | + | |
| 231 | + | |
232 | 232 | | |
233 | 233 | | |
234 | 234 | | |
235 | 235 | | |
| 236 | + | |
| 237 | + | |
| 238 | + | |
236 | 239 | | |
237 | 240 | | |
238 | 241 | | |
239 | 242 | | |
240 | 243 | | |
241 | | - | |
242 | | - | |
| 244 | + | |
| 245 | + | |
243 | 246 | | |
244 | 247 | | |
245 | 248 | | |
246 | 249 | | |
247 | | - | |
| 250 | + | |
248 | 251 | | |
249 | 252 | | |
250 | 253 | | |
251 | 254 | | |
252 | | - | |
| 255 | + | |
253 | 256 | | |
254 | | - | |
255 | | - | |
256 | | - | |
| 257 | + | |
| 258 | + | |
| 259 | + | |
257 | 260 | | |
258 | | - | |
259 | | - | |
| 261 | + | |
| 262 | + | |
| 263 | + | |
| 264 | + | |
260 | 265 | | |
261 | 266 | | |
262 | 267 | | |
| |||
0 commit comments