nickva commented on issue #5585: URL: https://github.com/apache/couchdb/issues/5585#issuecomment-3036875966
Thanks for reaching out @feliixx. More open dbs is an expected behavior https://github.com/apache/couchdb/pull/5402. Set a maximum dbs open that suites your case and they'll be replace / cycled in an LRU fashion. There was a recent issue regarding high memory usage as well related to a `nofiles` `ulimit` interaction with a large (unlimited ulimit from OS). https://github.com/apache/couchdb/pull/5575. But that seems mostly docker related, but worth checking out just in case. I am not entirely sure about the higher CPU usage. The databases being open but idle, shouldn't add a lot more CPU usage in general. Do you see any other corresponding changes - more throughput, more disk I/O usage. Any change or differences with request latency. It could be an Erlang behavior change perhaps, how scheduling works and such. To specifically reduce CPU usage could try these settings in vm.args (uncomment those): https://github.com/apache/couchdb/blob/420a577ace6a59a0febc20de6b4195f1754fc358/rel/overlay/etc/vm.args#L80-L85. That's usually a good idea to use in docker or case when there is a CPU quota, and busy waiting to reduce latency works against the quota and consumes it leaving less of it to do useful work. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
