zsh-workers
 help / color / mirror / code / Atom feed
From: Zeshy <ml.zsh@gmx.es>
To: zsh-workers@zsh.org
Subject: [BUG] APPEND_HISTORY leads to complete reread + rewrite of histfile
Date: Wed, 6 Dec 2017 20:31:23 +0100	[thread overview]
Message-ID: <20171206193122.w4r3dhkotlhdtrah@local> (raw)

Hi all!

In search of the reason why zsh (5.4.2 and fairly recent git) is
so much slower reading/writing larger history files (13 MB, 330k lines)
than bash (4.4.12), I think I found a bug. If I missed something (like
some option), and this is not a bug, but just misconfiguration, or if
you need more information, please let me know.


When configured to *append* the history on exit with the following
config:

---------------- BEGIN .zshrc -----------------
#!/usr/bin/zsh
HISTFILE="/var/tmp/.histfile"
HISTSIZE=9223372036854775807 # LONG_MAX (limits.h)
SAVEHIST=9223372036854775807 # LONG_MAX (limits.h)
setopt append_history
setopt extended_history
unsetopt hist_save_by_copy
unsetopt inc_append_history_time
---------------- END .zshrc -----------------

zsh (with "-d" or without) seems to do the following:

Step 1) append to history file
Step 2) read complete history file
Step 3) write complete history file

This seems to be invariant to
- option HIST_SAVE_BY_COPY,
- option INC_APPEND_HISTORY_TIME,
- values of HISTSIZE and SAVEHIST (tried with 500000 for both).

With "unsetopt APPEND_HISTORY", only step 3 is executed, as expected.


I interspersed some debug printf's in Src/hist.c and saved the output
of simply starting zsh and hitting Ctrl-D (exit). Absolute and relative
times are in milliseconds.

URLs:

https://pastebin.com/BzJhrr69  .zshrc-appendhistory
https://pastebin.com/ULCt7XcR  .zshrc-noappendhistory
https://pastebin.com/bHTqQu0C  hist.c
https://pastebin.com/QUjZ98Zn  zsh-appendhistory--debug-output.txt
https://pastebin.com/VUpGf6Fa  zsh-noappendhistory--debug-output.txt


Zeshy


             reply	other threads:[~2017-12-06 19:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-06 19:31 Zeshy [this message]
2017-12-06 19:51 ` Bart Schaefer
2017-12-06 19:52   ` Bart Schaefer
2017-12-21 20:52   ` Zeshy

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=20171206193122.w4r3dhkotlhdtrah@local \
    --to=ml.zsh@gmx.es \
    --cc=zsh-workers@zsh.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 public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).