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

Haproxy and tomcat JSESSIONID

One of the biggest problems I have been trying to solve at our startup is to put our tomcat nodes in HA mode. Right now if a customer comes, he lands on to a node and remains there forever. This has two major issues: 1) We have to overprovision each node with ability to handle worse case capacity. 2) If two or three high profile customers lands on to same node then we need to move them manually. 3) We need to cut over new nodes and we already have over 100+ nodes.  Its a pain managing these nodes and I waste lot of my time in chasing node specific issues. I loath when I know I have to chase this env issue. I really hate human intervention as if it were up to me I would just automate thing and just enjoy the fruits of automation and spend quality time on major issues rather than mundane task,call me lazy but thats a good quality. So Finally now I am at a stage where I can put nodes behing HAProxy in QA env. today we were testing the HA config and first problem I immediat...

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 ...

Spring 3.2 quartz 2.1 Jobs added with no trigger must be durable.

I am trying to enable HA on nodes and in that process I found that in a two test node setup a job that has a frequency of 10 sec was running into deadlock. So I tried upgrading from Quartz 1.8 to 2.1 by following the migration guide but I ran into an exception that says "Jobs added with no trigger must be durable.". After looking into spring and Quartz code I figured out that now Quartz is more strict and earlier the scheduler.addJob had a replace parameter which if passed to true would skip the durable check, in latest quartz this is fixed but spring hasnt caught up to this. So what do you do, well I jsut inherited the factory and set durability to true and use that public class DurableJobDetailFactoryBean extends JobDetailFactoryBean {     public DurableJobDetailFactoryBean() {         setDurability(true);     } } and used this instead of JobDetailFactoryBean in the spring bean definition     <bean i...