Nick Vatamaniuc
Nick Vatamaniuc
@Sliosh it's still a good idea, yeah. For replication, it's hard to tell if it will improve the performance much. The client there already manages a pool of http(s) connections,...
We'd have to make sure packaging works well with the change. Run a full ci build (git checkout to `jenkins-*` brach and then `git commit --amend --no-edit && push`). I...
> I tried too, but I got an error for CentOS 8, because it's landed on the ARM64 worker and because it is using SM60, it failed. See https://ci-couchdb.apache.org/job/jenkins-cm1/job/FullPlatformMatrix/job/jenkins-sm-v128-default-version/1/pipeline-console/?selected-node=409 >...
> Do we have an option for CentOS 8 to update SM to a version > 60? Ideally we shouldn't have to. CentOS 8 should be shipping with its original...
> The goal here is to make our test suite test non-couchdb API implementations like pouchdb-server. 100%! Great idea to test the two together
Replication jobs not appear in be in `_active_tasks` if they crash too often and are penalized. That endpoint only shows job which are actively running. The more failed starts a...
A good idea to investigate @Benjamin-Philip With the built-in script I still see that the nif is faster even with the jit. Without the jit it's even more pronounced. Maybe...
> Could you share the parameters you benchmarked with so that I can investigate? I am using ``` ./test/benchmark.escript 1 100 10000 60 nif : 4803827309 bytes / 60 seconds...
@Benjamin-Philip thanks for additional benchmarking and confirming the results. I liked the idea of generating the benchmark data separately and did that and replaced the script with a call to...
We don't currently have an internal health check or alarm system. It's not a bad idea to have it, in principle, but since there is no such application or API...