So I think for the moment I'll keep the format unless a reviwer demands something different. I think it is simply more transparent and this is a technical article. There are many benchmarks involving collapse here (github.com/fastverse/fa...), some of which use visual modes of presentation.

And I do have an overall space constraint with this article, which is at 32 pages now. So the only way would be compressing multiple operations in a plot (like duckdb benchmarks). While this may be nice, it does not make for easy syntax comparison and interpretation either.

Ok, thanks for elaborating. I agree that a plot would be nicer, though not necessarily easier to read. Take for example the grouped median benchmark. dplyr's runtime was 5.62s, collapse was 14.6ms - that's a factor ~400. To present that on a plot, it would have to be logarithmic...

Ok, thanks. And that's interesting. What do you find difficult about them?

The issue I have with plots is that they are more space consuming, and show one kind of information, wheras the tables have at least 3 useful information: Average and median runtime and memory consumption.