Reduce the logging on 2.0 (or increase the default logging params i.e num_files, size of each log)

We are logging heavily on default setup of 2.0.
This has too impacts:-
1) Front end Performance (needs to be proved, by how much). Perf team run tests with logging disabled
2) Useful/Relevant logs are rolled over extremely fast.

For example couchdb.logs:-
Every view query gets logged
[couchdb:info,2012-10-09T10:39:04.948,ns_1@10.6.2.39:<0.2898.720>:couch_log:info:39]10.6.2.42 - - POST /_view_merge/?stale=ok&limit=500 200
[couchdb:info,2012-10-09T10:39:04.949,ns_1@10.6.2.39:<0.5253.689>:couch_log:info:39]10.6.2.40 - - POST /_view_merge/?stale=ok&limit=500 200

From debug.logs:-
The same logs are present here as well, which are present in couchdb.info logs:-
[couchdb:info,2012-10-09T11:52:19.685,ns_1@10.6.2.39:<0.24278.786>:couch_log:info:39]10.3.2.5 - - GET /default/_design/d1/_view/v1?stale=ok&limit=500 200
[couchdb:info,2012-10-09T11:52:19.693,ns_1@10.6.2.39:<0.24279.786>:couch_log:info:39]10.3.2.5 - - GET /saslbucket/_design/d11/_view/v1?stale=ok&limit=10 200

Currently one could increase the values of the following params to keep more logs around,
but has space implications

.

.