3 ms·
Yeah, I think Fair comparisons are: * How do these things perform by default. This is how they're going to perform for many users, because if it's adequate nob
by tialaramex 4y ago
Yeah, I think Fair comparisons are:
* How do these things perform by default. This is how they're going to perform for many users, because if it's adequate nobody will tune them, why bother.
* How do these things perform with performance configuration as often recommended online. This is how they'll perform for people who think they need performance but don't tune or don't know how to tune, this might be worse than default but that's actually useful information.
* How do these things perform when their authors get to tune them for our test workload. This is how they'll perform for users who squeeze every drop and can afford to get somebody to do real work to facilitate, possibly even hiring the same authors to do it.
In some cases I would also really want to see:
* How do these things perform with recommended security. A benchmark mode with great scores but lousy security can promote a race to the bottom where everybody ships insecure garbage by default then has a mode which is never measured and has lousy performance yet is mandatory if you don't think Hunter2 is a great password.
- mholt 4y ago> How do these things perform by default. Agreed on this one -- today I'm looking at how to disable metrics by default and make them opt-in. At least until the performance regression can be addressed. Update: PR opened: https://github.com/caddyserver/caddy/pull/5042 https://github.com/caddyserver/caddy/pull/5042 - hoping to land that before 2.6.
- dQw4w9WgXcQ 4y agoGood stuff dude. Listens to users, sees a problem, doesn't take it personally, makes a fix. Caddy's going places.
- mholt 4y agoI'm also grateful that Dave, the original contributor of the metrics feature, isn't taking it personally. We love the functionality! Just gotta refine it...