Github user robertkowalski commented on the pull request:
https://github.com/apache/couchdb-couch/pull/57#issuecomment-114837039
I am working with the lager team to improve the performance of lager itself
now.
@kxepal I don't want to discourage you and see your good intentions
regarding building a full featured benchmark suite **before** doing any further
performance work.
I think a automatic testsuite will evolve automatically as soon as enough
people in the project **care** about performance. We can build the best
monitoring/benchmarking whatever tool and throw it in front of the community -
as long as nobody **cares** about performance, they won't use it. One example
for that is https://github.com/apache/couchdb/tree/master/test/bench which
already provides some performance tests, a few moths ago I deleted half of them
because they were broken since years and nobody noticed, as nobody uses them. I
am not sure what the future for another testsuite is, if I build it right now.
Just to clarify: I am not saying it is a bad idea to have a full featured
benchmark suite, but I think it will appear automatically on a way to more
performance where more and more people care about performance and do
performance related work and working on that testsuite should not block work
from people that care about performance.
For me that means working further on low-hanging fruits where a performance
improvement is easily observable even with a small microbenchmark. I hope that
more and more people in the project see how much we can CouchDB's performance
and jump onto that wagon. Throwing a testsuite in front of them probably does
not motivate most people to start to care about performance, as it is an
additional tool that can help people that are working on performance
improvements.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
