From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: org-mode on sloooow computer Date: Sat, 25 Apr 2009 05:51:48 +0200 Message-ID: References: <87hc0fe35v.fsf@eeepc.chemeng.ucl.ac.uk> <5A8DAF72-27D1-4BC5-B70C-884E2F98620B@gmail.com> <18928.59232.992700.573573@pinto.chemeng.ucl.ac.uk> <18929.30496.879823.967736@pinto.chemeng.ucl.ac.uk> <49F1C0AD.7090309@diplan.de> <18929.57089.531617.730982@pinto.chemeng.ucl.ac.uk> <3F3FAB94-BF93-4BC5-8698-4240A21FA67F@gmail.com> <18930.15516.830598.234897@pinto.chemeng.ucl.ac.uk> Mime-Version: 1.0 (Apple Message framework v930.3) Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LxYvn-00039O-FJ for emacs-orgmode@gnu.org; Fri, 24 Apr 2009 23:51:59 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LxYvj-00038v-08 for emacs-orgmode@gnu.org; Fri, 24 Apr 2009 23:51:58 -0400 Received: from [199.232.76.173] (port=54399 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LxYvi-00038s-Qa for emacs-orgmode@gnu.org; Fri, 24 Apr 2009 23:51:54 -0400 Received: from mail-ew0-f162.google.com ([209.85.219.162]:45756) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LxYvi-0002Mt-6c for emacs-orgmode@gnu.org; Fri, 24 Apr 2009 23:51:54 -0400 Received: by ewy6 with SMTP id 6so1287516ewy.42 for ; Fri, 24 Apr 2009 20:51:53 -0700 (PDT) In-Reply-To: <18930.15516.830598.234897@pinto.chemeng.ucl.ac.uk> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: e.fraga@ucl.ac.uk Cc: emacs-orgmode@gnu.org, Rainer Stengele On Apr 25, 2009, at 12:26 AM, Eric S Fraga wrote: > Carsten Dominik writes: >> Hmmm, `org-up-heading-all' still gets called, this should no longer >> happen. >> I wonder why, when. > > There must have been an error in recompilation after pulling the > updates with git. Although I asked emacs to recompile the directory, > it must have done something strange. I've cleared out the elc files > and compiled the whole directory and this is what I get now (which > indicates yet another improvement!): > > org-agenda 1 1.114424 > 1.114424 > org-agenda-list 1 0.889913 > 0.889913 > org-dblock-write:clocktable 7 0.586827 > 0.0838324285 > org-get-clocktable 1 0.427968 > 0.427968 > org-update-dblock 1 0.3902330000 > 0.3902330000 > org-prepare-agenda-buffers 2 0.267907 > 0.1339535 > org-agenda-get-day-entries 6 0.255334 > 0.0425556666 > org-agenda-get-restriction-and-command 1 0.224329 > 0.224329 > org-clock-sum 6 0.195653 > 0.0326088333 > org-agenda-get-scheduled 6 0.145536 > 0.024256 > org-prepare-agenda 1 0.128176 > 0.128176 > org-refresh-category-properties 12 0.0830839999 > 0.0069236666 > org-get-tags-at 8 0.059022 > 0.00737775 > org-up-heading-safe 21 0.0560520000 > 0.0026691428 > org-get-entries-from-diary 1 0.042899 > 0.042899 > ... > >> If you want to help: >> >> 1. reload uncompiled-code: >> >> C-u C-c C-x r > > Ummm, this doesn't work for me? C-c C-x r is undefined. You need to be in an org-mode buffer for this.. > >> 2. Arm the function >> >> M-x debug-on-entry RET org-up-heading-all RET >> >> 3. TUrn on debugging on error (needed, but hard to explain here) >> >> You can best do this from the "Options" menu, "Enter Debugger on >> Error" >> >> 4. Produce your agenda. You will get a backtrace buffer, which I >> would like to see... > > I don't get a backtrace buffer, which I guess now makes sense since > org-up-heading-all doesn't seem to get invoked any more. yes.. > >> if you want to hunt for more improvements, looking at >> this table, much can be gained by turning off the >> clocktable in the agenda and only turning it on >> interactively with "R" when you really need it. > > Yep, this helps as well: > > org-agenda 1 0.963539 > 0.963539 > org-agenda-list 1 0.739349 > 0.739349 > org-finalize-agenda-entries 1 0.286326 > 0.286326 > org-agenda-highlight-todo 8 0.282616 > 0.035327 > org-agenda-get-day-entries 6 0.2574450000 > 0.0429075000 > org-agenda-get-restriction-and-command 1 0.224016 > 0.224016 > org-agenda-get-scheduled 6 0.147105 > 0.0245175 > org-prepare-agenda 1 0.1283210000 > 0.1283210000 > org-prepare-agenda-buffers 1 0.1202870000 > 0.1202870000 > org-get-tags-at 8 0.059197 > 0.007399625 > org-up-heading-safe 21 0.056139 > 0.0026732857 > org-get-entries-from-diary 1 0.043058 > 0.043058 > ... > > However, I may actually leave the clock display on by default as it > has a psychological effect that is worthwhile for my working > practices; but at least I know that turning it off might be worthwhile > on the Asus. Of course, this i what I meant. > > In any case, I am impressed: from 4.5 seconds to less than a second in > one day! Can you do the same for my 2+ day optimisation runs I > require in my research? ;-) :-) Someone needs to write a profiler for that. In fact, clocking your work and looking at the biggest time consumers may help :-) Thanks, this was a fun day. - Carsten