app.js

var stream = require('getstream');
client = stream.connect('key', 'secret', 'id', { location: 'eu-central' });

var feed = client.feed('user', 'foobar');
var counter = 20;
var results = [];
function fetchFeed() {
  var start = new Date().getTime();
  feed.get({limit:20}).then(function(data) {
    results.push(new Date().getTime() - start);
    process.stdout.write(".");
    if (counter-- > 0)
      fetchFeed();
    else
      console.log((results.reduce(function(a, b) { return a + b; }) / results.length) + "ms");
  });
}

fetchFeed();

Alright. But this is relevant for all of your client libraries I guess? Have you looked at some of the ways to decrease SSL latency, such as false start and resumption (https://istlsfastyet.com/)? I imagine many of your clients being returning clients (as long as we're talking backend servers) meaning such approaches could be quite beneficial.

we already support this server side and on some clients. The Python client for instance does false start and reuses the connection making the SSL only free. We should be able to get similar results with the node client (researching on this right now)

Cool! Great job identifying the issue so fast!