Jul 29, 2020 | 2 min read
Due to the team’s focus on DrupalCon Global in the last couple of weeks, we’ve got a triple release to cover here (so apologies for being a little late!)
Another target area for recent work has been in improving performance – whether it’s the underlying infrastructure or the Lagoon components themselves.
Lagoon 1.8.x brings an important (and much asked-for) improvement in the performance of the User Interface. We have added a caching system to the group lookup queries (used in the UI, and some underlying CLI/GraphQL requests). Our testing has shown that this will improve the performance of the API between 5 and 20 times – meaning faster loads, smoother workflows and less DB traffic.
On the theme of reducing traffic, our good friend Blaize at Amazee Labs has been at it again – this time developing a new endpoint that can be used to perform status checks for sites running on Lagoon. Accessed at www.yoururl.com/.lagoonhealthz – it will return a tiny JSON payload that reports the health of the underlying components of that site – including NGINX, PHP, MariaDB, Solr and Redis services. The massive advantage of this is that we can use this URL to point external uptime checks to – which will reduce the unnecessary page loads and Drupal bootstraps, whilst making use of smart caching to provide the best balance of performance and accuracy. We’re pretty excited to measure what reduction in impact this can have on the myriad of external checkers that are being run on Lagoon sites around the clock (approximately 10% of origin hits can be attributed to status and uptime checks)
Questions? Comments? Feature requests? Get in touch with us anytime.