emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Samuel Loury <konubinix@gmail.com>
To: Eric S Fraga <e.fraga@ucl.ac.uk>
Cc: emacs-orgmode@gnu.org
Subject: Re: "atomic knowledge" modeling tool
Date: Mon, 29 Feb 2016 14:31:21 +0100	[thread overview]
Message-ID: <87y4a363ti.fsf@gmail.com> (raw)
In-Reply-To: <8737si5a4o.fsf@delle7240.chemeng.ucl.ac.uk>

[-- Attachment #1: Type: text/plain, Size: 1308 bytes --]

Eric S Fraga <e.fraga@ucl.ac.uk> writes:

> On Monday, 22 Feb 2016 at 10:04, Samuel Loury wrote:
>
> [...]
>
>> Reproducing a slow behavior is not easy. Today, the agenda is produced
>> in about 10s with almost the same contents. I included the profiler
>> report anyway, hoping that you will find something useful in it.
>>
>> - command-execute                                                3301  91%
>
> [...]
>
>>        - ad-Advice-org-agenda                                    2868  79%
>>         - #<compiled 0x25a8d89>                                  1922  53%
>>          - byte-code                                             1922  53%
>
> out of curiousity, what or how are you advising org-agenda?

I add two advises on top of org-agenda. The first one, executed before,
compute a set of contexts to filter the agenda view. The second,
is executed after and add coloring text-properties to help separating
the available contexts.

> also, the profile information would be most useful without compiled
> code (although obviously slower...).

I will clean the *elc files and send another report. I will also
deactivate the advises not to pollute the results.

-- 
Konubinix
GPG Key    : 7439106A
Fingerprint: 5993 BE7A DA65 E2D9 06CE  5C36 75D2 3CED 7439 106A

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 472 bytes --]

  reply	other threads:[~2016-02-29 13:31 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-29 18:21 "atomic knowledge" modeling tool luke call
2016-01-31 12:32 ` Eric S Fraga
2016-02-01 22:15   ` luke call
2016-02-02  8:49     ` Eric S Fraga
2016-02-03  9:33     ` Marcin Borkowski
2016-02-03 14:47       ` luke call
2016-02-03 17:15     ` Bingo UV
2016-02-03 18:22       ` luke call
2016-01-31 15:37 ` Ramon Diaz-Uriarte
2016-02-01 21:25   ` luke call
2016-02-03  8:04     ` Ramon Diaz-Uriarte
2016-02-02  7:23 ` Robert Klein
2016-02-02 15:20   ` luke call
2016-02-16 14:14     ` Samuel Loury
2016-02-16 16:18       ` Eric S Fraga
2016-02-16 16:44       ` Nicolas Goaziou
2016-02-16 19:52         ` Eric S Fraga
2016-02-20 18:09         ` Samuel Loury
2016-02-21 11:21           ` Nicolas Goaziou
2016-02-22  9:04             ` Samuel Loury
2016-02-24 16:46               ` Eric S Fraga
2016-02-29 13:31                 ` Samuel Loury [this message]
2016-03-06 19:26                   ` Samuel Loury
2016-03-07 15:28                     ` Eric S Fraga
2016-03-10  8:01                       ` Samuel Loury
2016-03-18 21:44                       ` Samuel Loury

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=87y4a363ti.fsf@gmail.com \
    --to=konubinix@gmail.com \
    --cc=e.fraga@ucl.ac.uk \
    --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).