Skip to main content

Managing User Perception in long running operations

Its important to manage User Perception properly and give him feedback if you are doing a long running synchronous operation. In the web world a user can get frustrated/impatient and try to do the same operation again leading to sending even more load on your server.

We recently ran into one issue like this where registration was taking a long time due to some server issue and looking into apache logs it was taking 10 sec but users were reporting it was taking 30-40 sec. Doing registration from a browser with empty cache confirmed that it was not registration but it was the confirmation page that was taking a long time and its a plain html page. It was all because the confirmation page was making 50 requests to the server to download images/js/css. The solution that clicked to me was simple, reduce the no of images, css, JS requests. The confirmation page was downloading all these images to
  1. 25 images/css/JS for rendering Header/Footer
  2. 5 images for rendering rounded corners
  3. 5-6 JS/css/images for google analytics and other stuff.
The solution was simple, we just whacked off the header and footer from confirmation page as it was not necessary and used CSS for rounded corners (Thanks to http://www.html.it/articoli/nifty/index.html for implementing rounded corners so easy and fast). Now registration was fast and users were happy. But it was still taking 10 sec that we are still working on to reduce, but to give user some feedback that we are doing some thing heavy on click on Register button, we are adding an Ajax popup to show Registering... (where ... is an animated gif) and we will mask out the entire screen so that user cant click on any of the buttons again.

One more example of user perception is when I was looking at Tomcat access log of one of our production servers and saw the same search request 4 times within 20 secs. The server was loaded heavily and the FullText keyword search was taking long time, due to user's successive 4 clicks it sent even more load on server and sending load average to spike through the roof.

The solution is simple and even applied by Microsoft, have you ever noticed when you are copying over 1G or more data then Windows will tell you it will take 2 min to copy the files and they show a progress bar but depending on your machine configuration and other activities that is going on it can take anywhere from 2 -3 min to do the copy. A normal user wont notice this small difference as he will see that something is going on. In our case things were not easy as Microsoft so for the time being we will disable the search button on the click and reenable it when results are downloaded.

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