Re: read_char() does not detect, handle special-event-map buffer changes

[Derek Upham]

Michael Albinus writes:

> Derek Upham <address@hidden> writes:
>
>> A couple of emails back I put in a D-Bus handler for asynchronous
>> messages.  I'll set it up to do nothing but push a timestamp onto a
>> list.  Then with a couple of dbus-send instances I can look for rate
>> differences between the two code paths.  I should have numbers this
>> weekend.
>
> Would be interesting. Alternatively, you could also stress via file
> notifications. Eval
>
> (defun my-inotify-handler (&rest args)
>   (message (format "Here I am '%s'" args)))
> (inotify-add-watch "/tmp" t 'my-inotify-handler)
>
> And in a shell outside Emacs, you call
>
> # while /bin/true; do touch /tmp/123; done

Neither my stock Emacs or experimental Emacs have inotify support, so I
went with D-Bus.  I fired off four processes in parallel, each spawning
in sequence 1001 dbus-send instances sending one signal.  The processes
ran for just over 5 seconds, so Emacs was handling around 800 signals
per second.

 | Metric                  |   Stock | Experimental |
 |-------------------------+---------+--------------|
 | average interval (usec) | 1249.68 |       1255.1 |
 | sum of intervals (usec) | 5002463 |      5024162 |

A graph shows essentially the same clustering for the two runs.  They
are both pretty steady.

interval-times.png
Description: interval times

Derek

-- 
Derek Upham
address@hidden