Skip to content

Compression ratio ambiguity in all charts #234

Description

@mqudsi

It would be greatly helpful if the compression ratio charts (e.g. https://quixdb.github.io/squash-benchmark/#ratio-vs-compression) included a hint on the "compression ratio" axis that said either "uncompressed:decompressed" or "higher scores are better" as it uses the opposite definition of "compression ratio" as compared to most other benchmarks (where the ratio is uncompressed/compressed) and to anyone that isn't familiar enough with an algorithm's performance on a particular dataset to orient themselves by seeing how it ranks (for example, I used cpp code with bzip2, which told me that there was no way 3.5 was uncompressed/compressed) wouldn't be able to figure out what's what.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions