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
This package is the “Swift Collections Benchmark”. But why tie it to “collections” at all? I understand that this was the impetus for this package, but it has uses well beyond collections. I would suggest renaming this the “Swift Benchmarks” (or something like that) and lose any implied suggestion that this benchmarking is for collections only.
For example, we might use this for testing any computationally intensive process, e.g., the benchmarking of pixel buffer processing, or benchmarking to determining the appropriate striding factor for a particular parallel calculation. The list is endless.
The text was updated successfully, but these errors were encountered:
I think "Swift Benchmarks" would be a bit too ambitious -- this package is for measuring how performance changes over a single variable, which is an important task, but "benchmarking" in general usually means far more than just that.
Additionally, the package in its current form really is mostly designed to target data structure analysis: for example, it assumes that the variable is some count of discrete items. (It even calls it "size".)
Generalizing things would certainly be an interesting project, though!
This package is the “Swift Collections Benchmark”. But why tie it to “collections” at all? I understand that this was the impetus for this package, but it has uses well beyond collections. I would suggest renaming this the “Swift Benchmarks” (or something like that) and lose any implied suggestion that this benchmarking is for collections only.
For example, we might use this for testing any computationally intensive process, e.g., the benchmarking of pixel buffer processing, or benchmarking to determining the appropriate striding factor for a particular parallel calculation. The list is endless.
The text was updated successfully, but these errors were encountered: