Skip to main content

Premature optimization

I have been assigned the task to increase the the performance of the application in my last 2 companies and from my past experience I believe in 80-20 code execution rule, i.e. in production most of the time its the 20% of the code that is being executed and the rest 80% is used rarely. Therefore before you embark on increasing the performance of the website
  1. You should know your customers
  2. You should know their usage patterns
  3. You should first collect statistics about what are the features that customers are using heavily
Don't try to guess which features are used, do a quantitative analysis and focus on only those features that are used heavily. Apache/Tomcat access logs can be your buddies in reaching the goal, take daily logs from last 2-3 months put them in mysql or any DB using some simple python/perl script and create some excel graphs and do a trend analysis. For example in the below graph of webdav usage, I would rather focus on optimizing the PROPFINDs first then other operations.

Writing simple code is hard, following KISS (http://en.wikipedia.org/wiki/KISS_principle) is tough, whenever you try to increase performance of a feature you compromise simplicity and make the code a bit more complex then it was before. Therefore I don't believe in premature optimization, Donald Knuth had said "We should forget about small efficiencies, say about 97% of the time: premature optimization is the root of all evil".

Every programmer should follow some basic programming guidelines for performance when writing code but he shouldn't be too obsessive about performance when writing code, I have seen people writing Java code like C. They would not use Java's Date datatype or ArrayList and will use long to store dates and arrays instead of arraylist everywhere. Now tell me this if you are developing some Admin screens,user profile screens for a website or you are developing some internal application to be used by a handful of people making 100-200 request in an hour, why would you spend so much time making the code worse and complex by optimizing it prematurely. Analyze your apache logs insanely and focus on features that are used by customers heavily. Take the first 10 culprits optimize them and then repeat the process till you feel no more juice can be squeezed from the lemon.To optimize the top culprits if you have to compromise simplicity then its ok but don't make the job for the guy who is going to maintain the code after you leave hard by prematurely optimizing the whole code base.

Ofcourse if you are designing a new feature in an application and you foresee that it's going to be used heavily then  keep scalability and performance in mind when architecting the application but keep the code simple and before releasing it do some load testing using Jmeter or Load Runner and profile the code using some tool like JProfiler and optimize only the hotspots (code that is being executed 80% of the time ;) ).

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