Blog
Categories
- Agile
- Best Practices
- Center of Excellence
- Cloud
- Featured
- Functional Testing and Automation
- Giveaway
- Healthcare IT
- HP
- HP Discover Conference
- HP Software Patches
- Latest News
- LoadRunner
- Methodology
- Mobile
- Northway Navigator Club News
- Operating Systems
- Performance Testing and Automation
- Quality Assurance
- Security
- Service Virtualization
- SiteScope
- Training
- TweakLR
- Uncategorized
- VuGen Code
Archives
- April 2019
- September 2018
- July 2018
- June 2018
- October 2017
- August 2016
- April 2015
- February 2015
- September 2014
- August 2014
- May 2014
- April 2014
- March 2014
- October 2013
- September 2013
- August 2013
- June 2013
- May 2013
- April 2013
- March 2013
- February 2013
- January 2013
- December 2012
- November 2012
- October 2012
- September 2012
- August 2012
- July 2012
- June 2012
- May 2012
- February 2011
- July 2010
- April 2010
- March 2010
- February 2010
- January 2010
- December 2009
- November 2009
- October 2009
- September 2009
- August 2009
- July 2009
- June 2009
- May 2009
- April 2009
- March 2009
- September 2007
- August 2007
- July 2007
- October 2006
- April 2006
- March 2005
- October 2004
- March 2004
- February 2004
- January 2004
- December 2003
- November 2003
- April 2003
-
Gone in 60 Seconds (or 8, or 2, or 400 ms)…
Posted on April 5, 2003 by Admin
Note: This article was originally posted on Loadtester.com, and has been migrated to the Northway web site to maintain the content online.
According to Robert B. Miller[1], here are acceptable response times for various actions:One tenth of a second (0.1) is about the limit for having the user feel that the system is reacting instantaneously, meaning that no special feedback is necessary except to display the result.
One second (1.0) is about the limit for the user’s flow of thought to remain uninterrupted, even though Read Entire Entry -