unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: antipov@mvista.com, emacs-devel@gnu.org
Subject: Re: immediate strings
Date: Sat, 26 Nov 2011 12:03:06 +0200	[thread overview]
Message-ID: <8339db8alh.fsf@gnu.org> (raw)
In-Reply-To: <4ED09DD4.1090201@cs.ucla.edu>

> Date: Sat, 26 Nov 2011 00:05:40 -0800
> From: Paul Eggert <eggert@cs.ucla.edu>
> Cc: emacs-devel@gnu.org
> 
> On 11/25/2011 06:15 PM, Dmitry Antipov wrote:
> > I think it's worth playing with such a
> > little complication.
> 
> This looks like a good thing to pursue.

If by "pursue" you mean creating a separate branch and letting people
play with it and report results, then I agree.

But if that means applying this to the trunk, based just on the
preliminary statistics reported by Dmitry, presumably for his usage
pattern and locale, then I think the gains are not substantiated
enough to justify the change.

FWIW, I'd like to see a much more detailed statistics, both for memory
usage and for speed of frequent operations, before I could make up my
mind on whether this kind of micro-optimization is justified.  YMMV.

See also the issue raised by Andreas regarding the effect of packing
`size' and `size_byte' as bit fields.  These members of Lisp strings
are accessed very frequently, including in the innermost code of the
display engine, and also elsewhere where performance counts.  IMO, we
should consider the results very carefully before deciding on such a
change.



  reply	other threads:[~2011-11-26 10:03 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-26  2:15 immediate strings Dmitry Antipov
2011-11-26  7:56 ` Andreas Schwab
2011-11-26  8:05 ` Paul Eggert
2011-11-26 10:03   ` Eli Zaretskii [this message]
2011-11-26 14:28     ` Stefan Monnier
2011-11-26 14:30   ` Dmitry Antipov
2011-11-26 21:13     ` Paul Eggert
2011-11-28  4:19       ` --with-wide-int Stefan Monnier
2011-11-28  7:56         ` --with-wide-int Paul Eggert
2011-11-28 16:52           ` --with-wide-int Stefan Monnier
2011-11-28 18:04             ` --with-wide-int Dan Nicolaescu
2011-11-28 18:34               ` --with-wide-int Eli Zaretskii
2011-11-28 19:35               ` --with-wide-int Stefan Monnier
2011-11-29  4:26                 ` --with-wide-int Stephen J. Turnbull
2011-11-29  7:35             ` --with-wide-int Paul Eggert

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=8339db8alh.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=antipov@mvista.com \
    --cc=eggert@cs.ucla.edu \
    --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 public inbox

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

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 read-only IMAP folder(s) and NNTP newsgroup(s).