emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nick Dokos <nicholas.dokos@hp.com>
To: =?utf-8?Q?Peter_M=C3=BCnster?= <pmlists@free.fr>
Cc: nicholas.dokos@hp.com, emacs-orgmode@gnu.org
Subject: Re: [RFC] warn time for appointments
Date: Fri, 23 Mar 2012 12:42:35 -0400	[thread overview]
Message-ID: <10199.1332520955@alphaville> (raw)
In-Reply-To: Message from =?us-ascii?Q?=3D=3Futf-8=3FQ=3FPeter=5FM=3DC3=3D?= =?us-ascii?Q?BCnster=3F=3D?= <pmlists@free.fr> of "Fri\, 23 Mar 2012 11\:27\:43 BST." <87fwczzk68.fsf@micropit.couberia.bzh>

Peter Münster <pmlists@free.fr> wrote:

> On Fri, Mar 23 2012, Ivan Kanis wrote:
> > I got no reply to my RFC and to my tentative patches. Does that mean
> > everybody is happy with the default 12 minutes warning time?
> No, I'm not happy with 12 minutes. But there is
> https://github.com/p-m/org-notify where you can have arbitrary warning
> times (seconds, weeks, whatever...).
> Does it fit your needs?
> (I'll ask Bastien for inclusion in contrib...)

BTW, I had done some simple performance measurements and hit some hiccups
previously. I just repeated them and I believe things are much improved:

org-notify-process                8           0.521915      0.065239375
org-notify-todo-list              8           0.512575      0.064071875
org-notify-make-todo              194         0.0485780000  0.0002504020

Another time

org-notify-process                11          1.6243200000  0.1476654545
org-notify-todo-list              11          1.516659      0.1378780909
org-notify-make-todo              596         0.2396870000  0.0004021593

and I've seen the avg time (last column) of org-notify-process go up to
0.22s, whereas before it used to be 5s or so, and even after the first
round of optimization that Peter did, it went down but still was over a
second (1.6s iirc). That caused significant hesitation when typing.

At this point,I do not notice any such hesitation - otoh, I'm sure I'm
not stressing it very much: that would require constructing a suitable
load generator, which I have not done.

But previously, things were bad enough that I had to turn off the notify
process. Now, I'm leaving it on and (mostly) not noticing that
it's there, so that's definitely progress.

Thanks Peter!

  parent reply	other threads:[~2012-03-23 16:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-04 13:51 Ivan Kanis
2012-03-23  9:05 ` Ivan Kanis
2012-03-23 10:27   ` Peter Münster
2012-03-23 15:59     ` Bernt Hansen
2012-03-23 16:42     ` Nick Dokos [this message]
2012-03-27 19:58       ` Peter Münster
2012-03-25  8:29     ` Ivan Kanis
2012-03-25  8:34       ` Bastien

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:

  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=10199.1332520955@alphaville \
    --to=nicholas.dokos@hp.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=pmlists@free.fr \
    --subject='Re: [RFC] warn time for appointments' \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Code repositories for project(s) associated with this 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).