How can I improve the subjective speed of my application?

Question

Today my co-worker noticed that when adding a decimal place to a progress indicator leads to the impression that the program is running faster than without. (i.e. instead of 1,2

Answer 1

Allow the user to do something else, while your application is processing data or waiting for a result. In application-scope you could allow to do some refinement of a search query or collect information for preparing next steps. Or just present some other "work" necessary to do or just some hints, documentation, statistics, entertainment..

Answer 2

Use one of those animated progress bars which look like they are doing something even when they aren't progressing. Also, as peSHIr said - print each filename that you copy and update it really fast - you could even fake it by cycling through a large string array N times a second.

Answer 3

Present some intermediate, interesting results first. "We've found 2,359 zetuyls matching your request, we're just calculating their future value".

I've seen transport reservation systems do that sort of thing quite nicely.

Answer 4

This effect can be very dramatic: doing relatively large amounts of work to give users a correct and often updating status of progress can of course slow down the actual running time of the application (screen updates, progress display needed calculations, etc) while still giving the user the feeling it takes less time.

Some of the things you could do in GUIs:

• make sure your application remains responsive (resizing the forms remains possible, perhaps give a cancel button for the operation?) while background processing is occurring
• be very consistent in showing status messages/hourglass cursors throughout the application
• if you have something updating during an operation, make sure it updates often (like the almost ridiculous showing of filenames and registry keys during an install), or make sure there's an option to make it do this for users that like this behavior

Answer 5

I've read somewhere that if the process seems to be speeding up, it seems to be faster than when it's progressing at a steady pace. I can't find the reference right now, but it should be simple to implement.

(10 minutes later...)

A further look down Google lane unearthed the following references:

http://www.azarask.in/blog/post/hacking-memory/ http://blogs.msdn.com/time/

Answer 6

Add a thread sleep at critical points. With each passing version, reduce the delay.