Skip to main content

Keep slogging help is on the way

When working in startup, don’t lose hope, keep slogging as once you reach scale help is on the way.

So far I have been scaling Mysql by throwing more hardware and focusing only on performance issues detected by new relic or my custom report but there were some data driven anomalies where 99% calls to this query would take 1sec but one call to same query would take 10sec.  I wasn’t focusing much on it because it was a blip in the graph and there were too many other issues to focus on.

Now we got a full time Mysql engineer who is looking at these queries and hunting down suspects. Today he found this query

select sum(points) from (
            select g.all_versions_size as points from folders_trash f
            inner join groups g on f.folder_id = g.folder_id
            union all
            select e1.size as points from groups_trash g1
            inner join entries e1 on g1.group_id=e1.group_id
            union all
            select e2.size as points from entries_trash e2
            ) s

Now this query works 99% of the time faster because most customers have very few data in trash but some customers have 400K+ rows in trash and for them this  was creating a temp table with 400K rows causing the blip.

Changing this query to something like below would create only 3 temp table row, the query became fast and uses less resources.

select sum(points) from (
            select sum(g.all_versions_size) as points from folders_trash f
            inner join groups g on f.folder_id = g.folder_id
            union all
            select sum(e1.size) as points from groups_trash g1
            inner join entries e1 on g1.group_id=e1.group_id
            union all
            select sum(e2.size) as points from entries_trash e2
            ) s

So don't lose hope, find creative ways initially like throwing more hardware to the problem if you can. When you reach scale expert help will come on the way :).

Comments

Popular posts from this blog

Killing a particular Tomcat thread

Update: This JSP does not work on a thread that is inside some native code.  On many occasions I had a thread stuck in JNI code and it wont work. Also in some cases thread.stop can cause jvm to hang. According to javadocs " This method is inherently unsafe. Stopping a thread with Thread.stop causes it to unlock all of the monitors that it has locked". I have used it only in some rare occasions where I wanted to avoid a system shutdown and in some cases we ended up doing system shutdown as jvm was hung so I had a 70-80% success with it.   -------------------------------------------------------------------------------------------------------------------------- We had an interesting requirement. A tomcat thread that was spawned from an ExecutorService ThreadPool had gone Rogue and was causing lots of disk churning issues. We cant bring down the production server as that would involve downtime. Killing this thread was harmless but how to kill it, t

Adding Jitter to cache layer

Thundering herd is an issue common to webapp that rely on heavy caching where if lots of items expire at the same time due to a server restart or temporal event, then suddenly lots of calls will go to database at same time. This can even bring down the database in extreme cases. I wont go into much detail but the app need to do two things solve this issue. 1) Add consistent hashing to cache layer : This way when a memcache server is added/removed from the pool, entire cache is not invalidated.  We use memcahe from both python and Java layer and I still have to find a consistent caching solution that is portable across both languages. hash_ring and spymemcached both use different points for server so need to read/test more. 2) Add a jitter to cache or randomise the expiry time: We expire long term cache  records every 8 hours after that key was added and short term cache expiry is 2 hours. As our customers usually comes to work in morning and access the cloud file server it can happe

Preparing for an interview after being employed 11 years at a startup

I would say I didn't prepared a hell lot but  I did 2 hours in night every day and every weekend around 8 hours for 2-3 months. I did 20-30 leetcode medium problems from this list https://leetcode.com/explore/interview/card/top-interview-questions-medium/.  I watched the first 12 videos of Lecture Videos | Introduction to Algorithms | Electrical Engineering and Computer Science | MIT OpenCourseWare I did this course https://www.educative.io/courses/grokking-the-system-design-interview I researched on topics from https://www.educative.io/courses/java-multithreading-for-senior-engineering-interviews and leetcode had around 10 multithreading questions so I did those I watched some 10-20 videos from this channel https://www.youtube.com/channel/UCn1XnDWhsLS5URXTi5wtFTA