Zsh Mailing List Archive Messages sorted by: Reverse Date, Date, Thread, Author

Re: Why sourcing a file is not faster than doing a loop with eval, zle -N

X-seq: zsh-users 22731
From: Sebastian Gniazdowski <psprint@xxxxxxxxxxx>
To: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
Subject: Re: Why sourcing a file is not faster than doing a loop with eval, zle -N
Date: Sat, 17 Jun 2017 16:56:10 +0200
Cc: Zsh Users <zsh-users@xxxxxxx>
In-reply-to: <etPan.594538f9.2ea629d6.10b2e@AirmailxGenerated.am>
List-help: <mailto:zsh-users-help@zsh.org>
List-id: Zsh Users List <zsh-users.zsh.org>
List-post: <mailto:zsh-users@zsh.org>
Mailing-list: contact zsh-users-help@xxxxxxx; run by ezmlm
References: <etPan.594513a8.516100cd.10b2e@zdharma.org> <CAH+w=7bVXtubcdwvEBC9isE32683dUipAUS=vrAkgO5pp2bkkw@mail.gmail.com> <CAH+w=7afTi=1bfLBCmq8-vB-rLWDtEkAtk8gCCna3-mQwZ1-Ow@mail.gmail.com> <etPan.594538f9.2ea629d6.10b2e@AirmailxGenerated.am>

17.06.2017 o 16:06:59, Bart Schaefer (schaefer@xxxxxxxxxxxxxxxx) napisał:
> You might get faster parsing if you setopt noaliases. Just a thought,
> can't try it right now.

I tried it. I think there's no change. Setup that reads ~/.fsh_cache is 0.414 vs 0.417 (noaliases). Before I've given time 0.432, but there was single large value 0.599, so I now summed 9 numbers, and divided by 9 (giving 0.414).

Just to remind, normal time is 0.396 (0.389 in second test).

Time for zcompiled ~/.fsh_cache is 0.375 in new test (previous: 0.383). So it's 20 ms compared to slower normal read 0.396. Almost reached the goal of 40 ms. For someone having startup time 200-250 ms the 40 ms would matter.

--  
Sebastian Gniazdowski
psprint /at/ zdharma.org

Follow-Ups:
- Re: Why sourcing a file is not faster than doing a loop with eval, zle -N
  - From: Sebastian Gniazdowski

References:
- Why sourcing a file is not faster than doing a loop with eval, zle -N
  - From: Sebastian Gniazdowski

Messages sorted by: Reverse Date, Date, Thread, Author