emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Johan Ekh <ekh.johan@gmail.com>
To: Nick Dokos <ndokos@gmail.com>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Slow usage of capture templates
Date: Wed, 2 Aug 2017 08:36:24 +0200	[thread overview]
Message-ID: <CAH13Zgi5nVVyzY+E=0fqhxS6zL9=C7jWnKGEPYiJEN-tO-2CBw@mail.gmail.com> (raw)
In-Reply-To: <8737gyrg6s.fsf@gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1668 bytes --]

Hi again, I tried with elp-instrument-package, see the results below. Seems
like function "org-get-x-clipboard" is taking a long time. CPU usage is
100% for the process "emacs-X11" during this time.

Does anyone have a clue what I should do?

BR / Johan



[image: Inline image 1]

On Wed, Jan 4, 2017 at 4:35 PM, Nick Dokos <ndokos@gmail.com> wrote:

> Johan Ekh <ekh.johan@gmail.com> writes:
>
> > Hi all
> >
> > I'm on Windows 10 with Cygwin-X and running Emacs 25.1.1 installed with
> Cygwin installer. Org-mode version is 9.0 installed from Elpa.
> >
> > I am experiencing very slow usage of my capture templates. When I hit
> C-c c my different templates show up but when I select one of them nothing
> happens for a long time then after 30-60
> > seconds it suddenly works as usual. This happens every time regardless
> of which template I select.
> >
> > When I start emacs without X, i.e. with the -nw flag, my capture
> templates works fast as usual.
> >
> > Does anyone know what I need to do?
> >
> > BR / Johan
> >
>
> First step is to probably profile org and see where time is spent:
>
> M-x elp-instrument package RET org RET
> ... then try a capture ...
> M-x elp-results
>
> Second step is to bring up a terminal and run htop in it, then try a
> capture and see if
> some process (maybe emacs, maybe something else) jumps up in CPU usage.
>
> Also try with a minimal org file and no other customizations: it may be
> that something
> in your configuration causes it (unless others can see the same slowness
> on similar systems).
>
> This kind of problem may take a long time to debug, so it's important not
> to get discouraged.
>
> --
> Nick
>
>
>

[-- Attachment #1.2: Type: text/html, Size: 2410 bytes --]

[-- Attachment #2: image.png --]
[-- Type: image/png, Size: 25426 bytes --]

  reply	other threads:[~2017-08-02  6:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-04  8:51 Slow usage of capture templates Johan Ekh
2017-01-04 15:35 ` Nick Dokos
2017-08-02  6:36   ` Johan Ekh [this message]
2017-08-02  6:51     ` Nicolas Goaziou
2017-08-02  7:10       ` Johan Ekh
2017-08-02 10:26         ` Johan Ekh
2017-08-02 10:55           ` Adam Porter
2017-08-02 13:32             ` Johan Ekh
2017-08-02 22:12               ` Tim Cross
2017-08-07  7:36                 ` Johan Ekh
2017-08-07  8:00                 ` Fabrice Popineau
2017-08-07  9:20                   ` Johan Ekh

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='CAH13Zgi5nVVyzY+E=0fqhxS6zL9=C7jWnKGEPYiJEN-tO-2CBw@mail.gmail.com' \
    --to=ekh.johan@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=ndokos@gmail.com \
    /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).