Shaving seconds off the response time

We already wrote about the outstanding features of Sentinel Hub and its speed and how we have to analyse, for each request, several hundred trillion pixels. Not an easy task. We were still not happy, so we’ve put in more effort to optimise, this time focusing on the infrastructure. We were able to shorten the response time for another 0.5–1 second.

On the following graphs, you can see the distribution of response times before and after the optimisation. For almost double amount of requests done, the response time dropped for more than half a second.

Before the optimisation
After the optimisation in February

Main improvements of the index and faster handling of the connections were done just in time before the huge wave of requests from Estonia, which was triggered by one of the posts on Facebook. The Estonian Maritime Administration Veeteede Amet posted an interesting information about ice conditions on the Estonian coast, accompanied with Sentinel-2 image created with our Image Browser. More than 10.000 Estonians clicked on the link. What is especially interesting is that they jointly created more than 600.000 requests in just 48 hours. It shows how interesting Sentinel-2 data are, if you give easy-to-use tools to people to analyse it.

The Estonian coast from above. Image created in Sentinel Playground, acquired on February 7, 2017.

You can check the speed of Sentinel Hub services on your own with Image Browser, which contains the archive of Sentinel-2 and Landsat-8 data.

Contact us for accessing also other Sentinel Hub tools or check our WMS/WCS services, so that you can access the global Sentinel-2 data without downloading anything.

Originally published at