From: Michael Welle <mwe012008@gmx.net>
To: emacs-orgmode@gnu.org
Subject: Re: working with tables can be quite painful...
Date: Mon, 19 Sep 2016 14:58:01 +0200 [thread overview]
Message-ID: <8760psm4h2.fsf@luisa.c0t0d0s0.de> (raw)
In-Reply-To: <87zin4z3u3.fsf@ucl.ac.uk> (Eric S. Fraga's message of "Mon, 19 Sep 2016 09:33:24 +0100")
Hello,
Eric S Fraga <e.fraga@ucl.ac.uk> writes:
> On Saturday, 17 Sep 2016 at 08:48, Nicolas Goaziou wrote:
>
> [...]
>
>> Could you send a profiler report so that I can get a better glimpse on
>> what part of `org-table-align' is lagging?
>
> Hi Nicolas,
>
> this morning, working on the same table is much less painful. I've run
> the profile and did some movements and changes to the table and here is
> the output from the profiler (I can send you the full report if you
> wish).
>
> I know that if I narrow the buffer to just the section (headline and
> contents) that contains the table, the performance is
> better. Anecdotally, it would seem that the performance degrades over
> time so I wonder if there is a cache issue?
the output of your profiler run doesn't ring a bell, but a few years ago
I had the problem that after some uptime (my Emacs uptime is typical
several days, up to a few weeks) Org operations like building the agenda
became sloooow. Restarting Emacs fixed that, until the problem occurred
again after some time.
If I remember correctly I asked the list for advise. But it looked like
one of these problems only I have ;). Maybe some other lisp package had
its hands in the game, I don't know. Eventually, after some Emacs, Org
and other updates the problem was gone.
As I said, I don't think, you suffer from the same problem. But you said
you don't use the newest software versions, so just in case.
Regards
hmw
next prev parent reply other threads:[~2016-09-19 12:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-16 14:53 working with tables can be quite painful Eric S Fraga
2016-09-17 8:48 ` Nicolas Goaziou
2016-09-17 15:22 ` Adam Porter
2016-09-17 15:37 ` Michael Brand
[not found] ` <9ae6591e2754413885a96e19c2455472@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2016-09-19 8:33 ` Eric S Fraga
2016-09-19 12:58 ` Michael Welle [this message]
[not found] ` <df2f3c4ad6a34890ad82cd1d0d557003@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2016-09-19 14:23 ` Eric S Fraga
2016-09-19 17:54 ` Michael Welle
2016-09-22 19:52 ` Nicolas Goaziou
[not found] ` <61c781eee3b64613a40a39b95bc54e63@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2016-09-19 8:36 ` Eric S Fraga
2016-09-20 8:54 ` Jacob Nielsen
[not found] ` <b05decb709ba4f64932ba34835b08056@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2016-09-20 9:03 ` Eric S Fraga
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8760psm4h2.fsf@luisa.c0t0d0s0.de \
--to=mwe012008@gmx.net \
--cc=emacs-orgmode@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/org-mode.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).