Responsiveness

Last updated April 01, 2023

Responsiveness as a concept of computer science refers to the specific ability of a system or functional unit to complete assigned tasks within a given time.^[1] For example, it would refer to the ability of an artificial intelligence system to understand and carry out its tasks in a timely fashion.^[2]

Vs performance

Software which lacks a decent process management can have poor responsiveness even on a fast machine. On the other hand, even slow hardware can run responsive software.

It is much more important that a system actually spend the available resources in the best way possible. For instance, it makes sense to let the mouse driver run at a very high priority to provide fluid mouse interactions. For long-term operations, such as copying, downloading or transforming big files the most important factor is to provide good user-feedback and not the performance of the operation since it can quite well run in the background, using only spare processor time.

Delays

Long delays can be a major cause of user frustration, or can lead the user to believe the system is not functioning, or that a command or input gesture has been ignored. Responsiveness is therefore considered an essential usability issue for human-computer-interaction (HCI). The rationale behind the responsiveness principle is that the system should deliver results of an operation to users in a timely and organized manner.

The frustration threshold can be quite different, depending on the situation and the fact that user interface depends on local or remote systems to show a visible response.

There are at least three user tolerance thresholds (i.e.):^[4]

0.1 seconds: under 0.1 seconds the response is perceived as instantaneous (high user satisfaction);
1.0 seconds: between 0.1 seconds and 1.0 second a slight delay is perceived, which is regarded as annoying in a local system but tolerated in a web interface that depends on a remote system for the response; this kind of delay usually does not interrupt user's flow of thoughts;
10 seconds: between 1 second and 10 seconds, user's flow of thoughts is interrupted (user productivity is severely impacted) but user is able to keep his/her attention focused on the task being performed;; over 10 seconds of wait is regarded as unacceptable as it usually interrupts the user's attention on task being performed.

Solutions to improve responsiveness

Although numerous other options may exist, the most frequently used and recommended answers to responsiveness issues are:

Optimizing the process that delivers the output by eliminating wasteful, unproductive output from the algorithm or method by which the result is produced.
A decent process management system, giving highest priority to operations that would otherwise interrupt the user's work flow, such as typing, onscreen buttons, or moving the mouse pointer. Usually there is enough "idle time" in between, for the other operations.
Using idle time to prepare for the operations a user might do next.
Let the user do something productive while the system is busy for instance, writing information in a form, reading a manual, etc. For instance, in a tabbed browser, the user can read one page while loading another.
Deliver intermediate results, before the operation is finished. For instance, a web page can already be operated before all images are loaded, which will take up the idle time which would otherwise be spent needlessly.
If some waiting is inevitable, a progress indicator can significantly reduce frustration. For short delays, an animated icon might be sufficient. Longer delays are better covered with a progress bar, or, if possible, the system should provide an approximation of the time that an operation is going to take before starting it.

Related Research Articles

An operating system (OS) is system software that manages computer hardware and software resources, and provides common services for computer programs.

Real-time computing (RTC) is the computer science term for hardware and software systems subject to a "real-time constraint", for example from event to system response. Real-time programs must guarantee response within specified time constraints, often referred to as "deadlines".

In computing, a process is the instance of a computer program that is being executed by one or many threads. There are many different process models, some of which are light weight, but almost all processes are rooted in an operating system (OS) process which comprises the program code, assigned system resources, physical and logical access permissions, and data structures to initiate, control and coordinate execution activity. Depending on the OS, a process may be made up of multiple threads of execution that execute instructions concurrently.

In the industrial design field of human–computer interaction, a user interface (UI) is the space where interactions between humans and machines occur. The goal of this interaction is to allow effective operation and control of the machine from the human end, while the machine simultaneously feeds back information that aids the operators' decision-making process. Examples of this broad concept of user interfaces include the interactive aspects of computer operating systems, hand tools, heavy machinery operator controls and process controls. The design considerations applicable when creating user interfaces are related to, or involve such disciplines as, ergonomics and psychology.

In computing, scheduling is the action of assigning resources to perform tasks. The resources may be processors, network links or expansion cards. The tasks may be threads, processes or data flows.

In user interface design for computer applications, a modal window is a graphical control element subordinate to an application's main window.

Telerobotics is the area of robotics concerned with the control of semi-autonomous robots from a distance, chiefly using television, wireless networks or tethered connections. It is a combination of two major subfields, which are teleoperation and telepresence.

RTLinux is a hard realtime real-time operating system (RTOS) microkernel that runs the entire Linux operating system as a fully preemptive process. The hard real-time property makes it possible to control robots, data acquisition systems, manufacturing plants, and other time-sensitive instruments and machines from RTLinux applications. The design was patented. Despite the similar name, it is not related to the Real-Time Linux project of the Linux Foundation.

In concurrent programming, an operation is linearizable if it consists of an ordered list of invocation and response events, that may be extended by adding response events such that:

The extended list can be re-expressed as a sequential history.
That sequential history is a subset of the original unextended list.

<span class="mw-page-title-main">System Idle Process</span> Kernel process in Windows NT operating systems

In Windows NT operating systems, the System Idle Process contains one or more kernel threads which run when no other runnable thread can be scheduled on a CPU. In a multiprocessor system, there is one idle thread associated with each CPU core. For a system with hyperthreading enabled, there is an idle thread for each logical processor.

<span class="mw-page-title-main">Spinning pinwheel</span>

The spinning pinwheel is a type of throbber or variation of the mouse pointer used in Apple's macOS to indicate that an application is busy.

In computing, preemption is the act of temporarily interrupting an executing task, with the intention of resuming it at a later time. This interrupt is done by an external scheduler with no assistance or cooperation from the task. This preemptive scheduler usually runs in the most privileged protection ring, meaning that interruption and resuming are considered highly secure actions. Such a change in the currently executing task of a processor is known as context switching.

In programming and software design, an event is an action or occurrence recognized by software, often originating asynchronously from the external environment, that may be handled by the software. Computer events can be generated or triggered by the system, by the user, or in other ways. Typically, events are handled synchronously with the program flow; that is, the software may have one or more dedicated places where events are handled, frequently an event loop.

In computing, reactive programming is a declarative programming paradigm concerned with data streams and the propagation of change. With this paradigm, it's possible to express static or dynamic data streams with ease, and also communicate that an inferred dependency within the associated execution model exists, which facilitates the automatic propagation of the changed data flow.

In computing job control refers to the control of multiple tasks or jobs on a computer system, ensuring that they each have access to adequate resources to perform correctly, that competition for limited resources does not cause a deadlock where two or more jobs are unable to complete, resolving such situations where they do occur, and terminating jobs that, for any reason, are not performing as expected.

In computing, a hang or freeze occurs when either a process or system ceases to respond to inputs. A typical example is when computer's graphical user interface no longer responds to the user typing on the keyboard or moving the mouse. The term covers a wide range of behaviors in both clients and servers, and is not limited to graphical user interface issues.

In computing, input/output is the communication between an information processing system, such as a computer, and the outside world, possibly a human or another information processing system. Inputs are the signals or data received by the system and outputs are the signals or data sent from it. The term can also be used as part of an action; to "perform I/O" is to perform an input or output operation.

DioneOS is a multitasking preemptive, real-time operating system (RTOS). The system is designed for microcontrollers, originally released on 2 February 2011 for the Texas Instruments TI MSP430x, and then on 29 March 2013 for the ARM Cortex-M3. Target microcontroller platforms have limited resources, i.e., system clock frequency of tens of MHz, and memory amounts of tens to a few hundred kilobytes (KB). The RTOS is adapted to such conditions by providing a compact and efficient image. The efficiency term here means minimizing further central processing unit (CPU) load caused by system use. According to this definition, the system is more effective when it consumes less CPU time to execute its internal parts, e.g., managing threads.

BatteryMAX is an idle detection system used for computer power management under operating system control developed at Digital Research, Inc.'s European Development Centre (EDC) in Hungerford, UK. It was created to address the new genre of portable personal computers (laptops) which ran from battery power. As such, it was also an integral part of Novell's PalmDOS 1.0 operating system tailored for early palmtops in 1992.

In distributed system and system resource, elasticity is defined as "the degree to which a system is able to adapt to workload changes by provisioning and de-provisioning resources in an autonomic manner, such that at each point in time the available resources match the current demand as closely as possible". Elasticity is a defining characteristic that differentiates cloud computing from previously proposed computing paradigms, such as grid computing. The dynamic adaptation of capacity, e.g., by altering the use of computing resources, to meet a varying workload is called "elastic computing".

References

↑ Weik, Martin H. (31 December 2000). Computer science and communications dictionary. Springer. p. 1484. ISBN 978-0-7923-8425-0 . Retrieved 17 November 2010.
↑ University of Tennessee (System). Space Institute; SIGART. (1988). Proceedings: the first International Conference on Industrial & Engineering Applications of Artif[i]cial Intelligence & Expert Systems : IEA/AIE-88 at the University of Tennessee Space Institute (UTSI), Tullahoma, Tennessee, June 1-3, 1988. Taylor & Francis US. p. 180. ISBN 978-0-89791-271-6 . Retrieved 17 November 2010.
↑ Jonas Bonér; Dave Farley; Roland Kuhn; Martin Thompson (September 16, 2014). "The Reactive Manifesto (v2.0)".
↑ Melius Weideman (2009). Website Visibility: The Theory and Practice of Improving Rankings. Chandos Publishing. ISBN 978-1-84334-473-5 . Retrieved 2021-11-04.

External links

This page is based on this Wikipedia article
Text is available under the CC BY-SA 4.0 license; additional terms may apply.
Images, videos and audio are available under their respective licenses.

[Weik2000-1] Weik, Martin H. (31 December 2000). Computer science and communications dictionary. Springer. p. 1484. ISBN 978-0-7923-8425-0 . Retrieved 17 November 2010.

[InstituteSIGART.1988-2] University of Tennessee (System). Space Institute; SIGART. (1988). Proceedings: the first International Conference on Industrial & Engineering Applications of Artif[i]cial Intelligence & Expert Systems : IEA/AIE-88 at the University of Tennessee Space Institute (UTSI), Tullahoma, Tennessee, June 1-3, 1988. Taylor & Francis US. p. 180. ISBN 978-0-89791-271-6 . Retrieved 17 November 2010.

[reactive-manifesto-3] Jonas Bonér; Dave Farley; Roland Kuhn; Martin Thompson (September 16, 2014). "The Reactive Manifesto (v2.0)".

[web-responsiveness-thresholds-4] Melius Weideman (2009). Website Visibility: The Theory and Practice of Improving Rankings. Chandos Publishing. ISBN 978-1-84334-473-5 . Retrieved 2021-11-04.

[1]

[2]

[3]

[4]