all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Size and length limits for Emacs primitive types and etc data?
Date: Tue, 05 Feb 2013 23:28:39 +0200	[thread overview]
Message-ID: <83a9ria1rs.fsf@gnu.org> (raw)
In-Reply-To: <m2txpqh96s.fsf@samograd.ca>

> From: Burton Samograd <burton@samograd.ca>
> Date: Tue, 05 Feb 2013 12:06:35 -0700
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> >> I think linked nature of elisp data structure cause very high rate of CPU
> >> cache miss (but I don't actually run any AMD/Intel CPU profilers).
> >
> > Prove it.
> 
> Here's an analysis of cache misses with pointer based data structures
> (linked list and trees):
> 
>   http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.25.9669
> 
> It's common knowledge that linked lists are not cache friendly, leading
> to creation of structures like Unrolled Linked Lists
> (http://en.wikipedia.org/wiki/Unrolled_linked_list) to help.

The relevant thing here is how Emacs Lisp programs fare in this
regard.



  parent reply	other threads:[~2013-02-05 21:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-22 22:06 Size and length limits for Emacs primitive types and etc data? Oleksandr Gavenko
2013-02-03 13:56 ` Aurélien Aptel
2013-02-03 19:16   ` Eli Zaretskii
2013-02-04 12:38     ` Aurélien Aptel
2013-02-04 15:57       ` Eli Zaretskii
2013-02-05  9:41         ` Oleksandr Gavenko
2013-02-05 18:14           ` Eli Zaretskii
2013-02-05 20:17             ` Oleksandr Gavenko
2013-02-05 21:35               ` Eli Zaretskii
2013-02-06 18:46               ` Stefan Monnier
     [not found]           ` <mailman.19079.1360088047.855.help-gnu-emacs@gnu.org>
2013-02-05 19:06             ` Burton Samograd
2013-02-05 20:04               ` Oleksandr Gavenko
2013-02-05 21:28               ` Eli Zaretskii [this message]
2013-02-05 22:25           ` Peter Dyballa

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=83a9ria1rs.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=help-gnu-emacs@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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.