Ollie Parsley

@OllieParsley@mstdn.social
2 Followers
2 Following
2 Posts
Dabble - Develop - Deploy ⚪ By day I'm an Engineering Manager @MeltwaterEng (he/him)
Websitehttps://ollieparsley.com
Twitterhttps://twitter.com/ollieparsley
Ollie ParsleyFeb 22, 2023
JairamFeb 22, 2023
If you use #slack
for team communication & #GoogleCalendar
for managing your day, then do checkout https://dontinterrupt.app/. Works like a charm and keeps me sane. Notifications are automatically silenced and I can properly pay attention to my appointment. #productivitytips #focus cc @OllieParsley
Don't Interrupt

Take control of annoying interruptions. Prevent interruptions by automatically setting your status, presence and Do Not Disturb settings by giving granular working hours and linking Google Calendars.

Don't Interrupt
Ollie ParsleyNov 25, 2022
Meltwater EngineeringNov 25, 2022

We've published part 3 of our "3 Petabyte Elastic upgrade without downtime" series! This week it's all about search performance and wildcards.

This blog post also introduces Johan, our third different author in the series!

https://underthehood.meltwater.com/blog/2022/11/25/how-we-upgraded-an-old-3pb-large-elasticsearch-cluster-without-downtime-part-3-search-performance-and-wildcards/

#elasticsearch #upgrade https://t.co/VcKDIU850W

How we upgraded an old, 3PB large, Elasticsearch cluster without downtime. Part 3 - Search Performance & Wildcards

This is part 3 in our series on how we upgraded our Elasticsearch cluster without any downtime and with minimal user impact. As part of the Elasticsearch Upgrade project, we needed to investigate the search performance improvements between the old and the new versions. Running an older version of Elasticsearch has presented many performance issues over the years and we hoped that upgrading to a more recent version would help. This blog post will describe how we tested the search performance of our new Elasticsearch cluster and the different optimizations we used to improve it. Specifically, we will focus on how we solved the major bottleneck for our use case: wildcards.