From: Nick Dokos <firstname.lastname@example.org>
To: =?utf-8?Q?Peter_M=C3=BCnster?= <email@example.com>
Cc: firstname.lastname@example.org, email@example.com
Subject: Re: notifications for todo items
Date: Sat, 25 Feb 2012 21:45:21 -0500 [thread overview]
Message-ID: <17232.1330224321@alphaville> (raw)
In-Reply-To: Message from =?us-ascii?Q?=3D=3Futf-8=3FQ=3FPeter=5FM=3DC3=3D?= =?us-ascii?Q?BCnster=3F=3D?= <firstname.lastname@example.org> of "Sun\, 26 Feb 2012 01\:09\:03 +0100." <email@example.com>
Peter Münster <firstname.lastname@example.org> wrote:
> On Sat, Feb 25 2012, Nick Dokos wrote:
> > A quick first impression: orgntf-process seems expensive. It seems
> > to take 100% of one core (I've got a quad-core processor) for three or
> > four seconds every fifty seconds. Unfortunately, the core is the same one
> > that's running emacs, so emacs stops responding for those three or four
> > seconds. I have disabled org-notify for now.
> How many lines do you have in your org-files?
> (I've about 200 and execution time is about 100ms.)
Roughly 7000 - I just added a task to clean things up, so it's now 7002 :-)
> I call now "(org-element-parse-buffer 'heading)", I hope it's faster for
> you. Is it faster, when the file is byte-compiled?
> Other ideas:
> - I could divide orgntf-process into several tasks, so that things run
> more smoothly.
> - You could call (org-notify-start -60), so the process will be called,
> when idle for one minute.
This sounds promising - I'll try this out in the next iteration.
> The file has a new home: https://github.com/p-m/org-notify
> There is now `orgntf-verbose' to see execution time of
OK - I'll try it out when I get a chance.
next prev parent reply other threads:[~2012-02-26 2:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-22 23:38 notifications for todo items Peter Münster
2012-02-23 1:28 ` Nick Dokos
2012-02-23 8:36 ` Peter Münster
2012-02-23 9:06 ` Nick Dokos
2012-02-25 0:08 ` Nick Dokos
2012-02-26 0:09 ` Peter Münster
2012-02-26 2:45 ` Nick Dokos [this message]
2012-02-26 5:04 ` Nick Dokos
2012-02-26 14:06 ` optimisation of org-notify (was: notifications for todo items) Peter Münster
2012-03-04 23:37 ` optimisation of org-notify Peter Münster
2012-02-26 9:33 ` notifications for todo items Nicolas Goaziou
2012-02-26 14:07 ` Peter Münster
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).