So since benchmarking is out, how do we then find out where
potential problems are.
What does OpenBSD developers do, since surely they don't benchmark :)
Maybe we should profile instead ?
I'm not very experienced with webservers, but here
how i would approach it.
1. i have a problem, i think about it where/what the problem could be
2 i check the logs - test my equipment
3. I create 1 or a few profiling tests / micro benchmarks to test my assumptions
or make certain i haven't misinterpreted my problems.
4. Step back and interpret results
5. think of other tests / micro benchmarks that could further enlighten me
and confirm/unconfirm(?) my "findings"
What i wouldnt do, is "design" a mother of a benchmark that covers
all the bases.
It's to hard to get right. It would take to much time.
How would OpenBSD dev's approach a issue.
How are issues generally searched for/ found out?
I imagine something like
OpenBSD dev works on the httpd daemon - asks for testing.
I find a problem, ex: it'd slow like heck - check configuration -
interfaces - logs
What now - i write back to dev.
dev asks me to do what?
What does the dev do behind the scenes?
regards mic
