I'm looking for an example of a job for which response time is important.

[One definition of response time is](https://www.cs.uic.edu/~jbell/CourseNotes/OperatingSystems/6_CPU_Scheduling.html):

> 
> The time taken in an interactive program from the issuance of a command to the **commence** of a response to that command.
> 
> 
> 

I've read that response time is important for interactivity, but I can't understand why. If the job isn't fully completed, what output could be produced that would be of interest to a user?

Wouldn't the user only care about how soon a job *finishes*, as that's the first time any output is produced?

For example, consider these two possible schedulings of two jobs:

```
Case 1: |---B---|---A---|
Case 2: |-A-|---B---|-A-|

```

Suppose that job A and B are issued at the same time, A being a command typed in by the user and B being some background process.

The response time for job A as I understand it would be shorter in case 2. As job A finishes (and produces output) at the same time in the two cases, I don't understand how the user benefits (or even notices) the better response time in case 2.