Conversation

Notices

1. clacke: inhibited exhausted pixie dream boy 🇸🇪🇭🇰💙💛 (clacke@libranet.de)'s status on Monday, 08-Apr-2024 23:57:49 EDT clacke: inhibited exhausted pixie dream boy 🇸🇪🇭🇰💙💛
   Once again pasting the beautiful waterpaint calligraphy of cyberciti.biz/humour/a-haiku-a… in the team chat.
   1. clacke: inhibited exhausted pixie dream boy 🇸🇪🇭🇰💙💛 (clacke@libranet.de)'s status on Tuesday, 09-Apr-2024 00:03:39 EDT clacke: inhibited exhausted pixie dream boy 🇸🇪🇭🇰💙💛

      in reply to

      I jokingly posted it the other day.

      100% a joke, there was no way it was DNS.

      Today I found a configuration line.

      It shouldn't matter, but just to exclude the impossible we had to try it.

      It was frikkin DNS.

      Not a network mesh latency issue, not a weird thing with the database, just some service (a shelf product, not our code) that incessantly looks up whatever names on every single request, without caching, and it was doing it from another continent, slowing everything to molasses.

      1. clacke: inhibited exhausted pixie dream boy 🇸🇪🇭🇰💙💛 (clacke@libranet.de)'s status on Tuesday, 09-Apr-2024 00:46:25 EDT clacke: inhibited exhausted pixie dream boy 🇸🇪🇭🇰💙💛

         in reply to

         "Why is it running well in Europe, but when we run it in Asia it's so slow? We checked container node specs and limit, db VM specs, everything is the same!"

         Turns out "everything is the same" was the problem, when the world around the container wasn't the same. 😅