[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: point-at-final-line
From: |
Eli Zaretskii |
Subject: |
Re: point-at-final-line |
Date: |
Mon, 29 Jan 2018 19:51:25 +0200 |
> From: Emanuel Berg <moasen@zoho.com>
> Date: Mon, 29 Jan 2018 17:40:38 +0100
>
> Eli Zaretskii wrote:
>
> > (But I'm sure that if you run each function
> > many times in a loop, you will see some
> > differences in timing. Right now, I think the
> > times are below your system clock resolution,
> > so you are measuring quantization noise.)
>
> Well, you know what they say, what you can't
> measure, you cannot control.
I'm saying that you _can_ measure this: just run each function many
times in a loop, and then divide the time by the number of iterations.
This is a standard method of timing short code fragments.
- Re: point-at-final-line, (continued)
- Message not available
- Re: point-at-final-line, Emanuel Berg, 2018/01/26
- Re: point-at-final-line, Marcin Borkowski, 2018/01/27
- Message not available
- Re: point-at-final-line, Emanuel Berg, 2018/01/27
- Re: point-at-final-line, Stefan Monnier, 2018/01/28
- Message not available
- Re: point-at-final-line, Emanuel Berg, 2018/01/28
- Re: point-at-final-line, Eli Zaretskii, 2018/01/28
- Message not available
- Re: point-at-final-line, Emanuel Berg, 2018/01/29
- Re: point-at-final-line, Eli Zaretskii, 2018/01/29
- Message not available
- Re: point-at-final-line, Emanuel Berg, 2018/01/29
- Re: point-at-final-line,
Eli Zaretskii <=
- Message not available
- Re: point-at-final-line, Emanuel Berg, 2018/01/29
- Re: point-at-final-line, Eli Zaretskii, 2018/01/29
- Re: point-at-final-line, Stefan Monnier, 2018/01/29
- Message not available
- Re: point-at-final-line, Emanuel Berg, 2018/01/30