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

RabbitMQ java clients for beginners

Here is a sample of a consumer and producer example for RabbitMQ. The steps are
Download ErlangDownload Rabbit MQ ServerDownload Rabbit MQ Java client jarsCompile and run the below two class and you are done.
This sample create a Durable Exchange, Queue and a Message. You will have to start the consumer first before you start the for the first time.

For more information on AMQP, Exchanges, Queues, read this excellent tutorial
http://blogs.digitar.com/jjww/2009/01/rabbits-and-warrens/

+++++++++++++++++RabbitMQProducer.java+++++++++++++++++++++++++++
import com.rabbitmq.client.Connection; import com.rabbitmq.client.Channel; import com.rabbitmq.client.*; public class RabbitMQProducer { public static void main(String []args) throws Exception { ConnectionFactory factory = new ConnectionFactory(); factory.setUsername("guest"); factory.setPassword("guest"); factory.setVirtualHost("/"); factory.setHost("127.0.0.1"); factory.setPort(5672); Conne…

Logging to Graphite monitoring tool from java

We use Graphite as a tool for monitoring some stats and watch trends. A requirement is to monitor impact of new releases as build is deployed to app nodes to see if things like
1) Has the memcache usage increased.
2) Has the no of Java exceptions went up.
3) Is the app using more tomcat threads.
Here is a screenshot

We changed the installer to log a deploy event when a new build is deployed. I wrote a simple spring bean to log graphite events using java. Logging to graphite is easy, all you need to do is open a socket and send lines of events.
import org.slf4j.Logger;import org.slf4j.LoggerFactory; import java.io.OutputStreamWriter; import java.io.Writer; import java.net.Socket; import java.util.HashMap; import java.util.Map; public class GraphiteLogger { private static final Logger logger = LoggerFactory.getLogger(GraphiteLogger.class); private String graphiteHost; private int graphitePort; public String getGraphiteHost() { return graphiteHost; } public void setGraphite…

What a rocky start to labor day weekend

Woke up by earthquake at 7:00 AM in morning and then couldn't get to sleep. I took a bath, made my tea and started checking emails and saw that after last night deployment three storage node out of 100s of nodes were running into Full GC. What was special about the 3 nodes was that each one was in a different Data centre but it was named same app02.  This got me curious I asked the node to be taken out of rotation and take a heap dump.  Yesterday night a new release has happened and I had upgraded spymemcached library version as new relic now natively supports instrumentation on it so it was a suspect. And the hunch was a bullseye, the heap dump clearly showed it taking 1.3G and full GCs were taking 6 sec but not claiming anything.



I have a quartz job in each jvm that takes a thread dump every 5 minutes and saves last 300 of them, checking few of them quickly showed a common thread among all 3 data centres. It seems there was a long running job that was trying to replicate pending…