Worse performance when enabling compression (on GCP + Elastic Cloud)

🐛 Bug Report

It seems that using the cloud authentication when creating the Client (instead of specifying an url) degrades performance in our case.

With an URL, the 90 percentile is around 80ms. With a Cloud ID, the 90 percentile is around 120ms.

This is reproducible : I can switch from an URL to a Cloud ID (see code below) and our perf test reports a performance degradation as seen above.

I have read that the cloud scheme enables compression and such, maybe this is the cause of the problem.

To Reproduce

Steps to reproduce the behaviour:

Creating the client:

new Client({
      cloud: {
        id: this.config.cloudId(),
        username: this.config.username(),
        password: this.config.password()
      },
      auth: {
        username: this.config.username(),
        password: this.config.password()
      }
    })

Previous code:

      return new Client({
        node: this.config.url()
      });
    }

Expected behavior

Performance should be the same in both case (connect with cloud or node).

Your Environment

• node version: 10.17.0
• @elastic/elasticsearch version: 7.5.0
• Elasticsearch Cloud : 7.5.1
• Google App Engine

[tomsquest]

Hey thanks @delvedor to have taken some times to check this.

I will try to reproduce this with what you have given, in the following days.

1. First test, on GAE, deploy your gist and test the actual performance
2. Use a larger dataset, maybe ours
3. Use a larger query set with a larger dataset
4. Use Nest+Fastify as the http server

Test will be run from Blazemeter as it is easier for me and I won’t run a perf test from my laptop 😃

[stale[bot]]

We understand that this might be important for you, but this issue has been automatically marked as stale because it has not had recent activity either from our end or yours. It will be closed if no further activity occurs, please write a comment if you would like to keep this going.

Note: in the past months we have built a new client, that has just landed in master. If you want to open an issue or a pr for the legacy client, you should do that in https://github.com/elastic/elasticsearch-js-legacy