Vladimir Smirnov

I think #743 should fix the problem, once it's merged. It introduced a config option that will send multiple targets in a single request. It however might need some work...

Since the issue was opened there were numerous changes in functions, I expect that this issue is now fixed. If not - please reopen with more details on how to...

I'm hoping to tag 0.16 in near future (once #742 is merged and once I finish changelog, as we are over 200 commits since last release and there were a...

Forgot to mention, but docker workflow is defined here: https://github.com/go-graphite/carbonapi/blob/main/.github/workflows/docker-ghcrio.yml

Ok... something is definitely wrong with the conditions for workflow and I have no idea what is that. I'll try to debug that in separate repos and will try to...

0.16.0-patch1 should be uploaded to the ghcr.io (thx to @deniszh for finding the last problem that caused failure). I think from now on process should be reliable enough.

Actually I would split the PR in 2, current one focuses on refactoring HTTP client (should fix keep-alive for failed requests and should ensure that not more than X connections...

As about single fetch request for multiple targets: I think #743 should fix the problem, once it's merged. It introduced a config option that will send multiple targets in a...

I wonder if you've also tried with combineMultipleTargetsInOne flag? https://github.com/go-graphite/carbonapi/blob/main/cmd/mockbackend/testcases/pr743/carbonapi.yaml#L15 But I'll have another look at why http client doesn't respect keepalive option.

Also a question - how unique are queries? You were mentioning that it's multiple targets, are all of the targets - unique? Or some percentage of targets is the same?...