all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: David Reitter <david.reitter@gmail.com>
To: Emacs devel <emacs-devel@gnu.org>
Subject: UI / reaction time - was: Re: 23 branch - can't push - lock
Date: Fri, 17 Jun 2011 15:19:40 -0400	[thread overview]
Message-ID: <CE8430C2-CBDB-402E-80E2-1F65F805FB8B@gmail.com> (raw)
In-Reply-To: <83sjr8wjow.fsf@gnu.org>

On Jun 17, 2011, at 11:39 AM, Eli Zaretskii wrote:
> How do you mean "discernible"?  Most humans are generally unable to
> react in less than 200-300ms, so 30ms is an order of magnitude off the
> mark.

Reaction requires a chain of not only perception and related encoding, but also planning possibly moderated by execute control, possibly memory access, motor planning and actual execution.  That takes time.  In some cases, after some reactions have been routinized, you can sidestep much of that, and react more quickly.  That said, not reactions are relevant, but change detection and perceived duration.   Current cognitive modeling frameworks assume a 50ms "clock" for cognitive processing (simple, IF-THEN rules, for instance, in Anderson's ACT-R), and this is where I derived this figure.  You may be right in that more than that  is needed to estimate relative duration, let alone be bothered by a wait.   Some people can perceive duration in a visual stimulus in around 100ms (a study by Efron in 1970 found 120ms as minimum).  Change detection seems to be similarly quick when subjects attend to the location (Pashler 1988).

We may both be missing the point with this, though.  At around 1s, isn't it much more about what users "feel" is fast or a delay, as opposed to whether they can make use of the actual speed-up?

The figures you obtained (less than 1 sec) seem OK to me (subjectively), while the pauses I experienced (several seconds) seemed unpleasant.  They were at a larger scale than that.

Thanks for the hints regarding speeding up bzr and undoing a commit.  I'll leave that portion of the discussion, as it has little to do with Emacs, as Stefan pointed out.




  reply	other threads:[~2011-06-17 19:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-16 15:49 23 branch - can't push - lock David Reitter
2011-06-16 16:28 ` David Reitter
2011-06-16 21:44   ` Glenn Morris
2011-06-16 17:27 ` Eli Zaretskii
2011-06-16 17:44   ` David Reitter
2011-06-16 20:09     ` Eli Zaretskii
2011-06-17 13:57       ` David Reitter
2011-06-17 15:39         ` Eli Zaretskii
2011-06-17 19:19           ` David Reitter [this message]
2011-06-17 21:59             ` UI / reaction time - was: " chad
2011-06-19 13:42           ` Stephen J. Turnbull
2011-06-17 16:30         ` Stefan Monnier

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CE8430C2-CBDB-402E-80E2-1F65F805FB8B@gmail.com \
    --to=david.reitter@gmail.com \
    --cc=emacs-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.