Hello, i got two windows machines: one is a surface with an i5 cpu and a desktop machine with an amd 6 core cpu. on both machines i have org mode 8.2.10. when i switch the prioity in an 15k line org file having 614kbyte in size on the i5 machine the system is really laggy and it takes up to two seconds changing the priority of todo headlines. on the desktop machine with a similar powerful cpu one a core level the changing is lightning fast. recently i got get the i5 machine also that fast by just adding the file again to the agenda list, but after restarting emacs it was slow again and now i cannot reproduce the same. does anyone have an idea what could be the reason here? thanks in advance. Michael
Hello,
Michael Ziems <sane@xiron.de> writes:
> i got two windows machines: one is a surface with an i5 cpu and
> a desktop machine with an amd 6 core cpu.
>
> on both machines i have org mode 8.2.10.
>
> when i switch the prioity in an 15k line org file having 614kbyte in
> size on the i5 machine the system is really laggy and it takes up to
> two seconds changing the priority of todo headlines. on the desktop
> machine with a similar powerful cpu one a core level the changing is
> lightning fast. recently i got get the i5 machine also that fast by
> just adding the file again to the agenda list, but after restarting
> emacs it was slow again and now i cannot reproduce the same.
>
> does anyone have an idea what could be the reason here?
No idea, but you could do some profiling and report the results here.
See `profiler-start'.
Regards,
--
Nicolas Goaziou
Hello,
thanks for the reply. is this information already helpful:
- command-execute 1331 92%
- call-interactively 1327 91%
- org-shiftdown 302 20%
- call-interactively 302 20%
- org-priority-down 302 20%
org-priority 302 20%
- org-shiftup 293 20%
- call-interactively 293 20%
- org-priority-up 293 20%
org-priority 293 20%
- next-line 183 12%
- funcall 183 12%
- #<compiled 0xc28a69> 183 12%
- line-move 183 12%
line-move-visual 180 12%
- org-cycle 145 10%
- org-cycle-internal-local 145 10%
- run-hook-with-args 108 7%
- org-optimize-window-after-visibility-change 104 7%
- org-subtree-end-visible-p 8 0%
- pos-visible-in-window-p 6 0%
- jit-lock-function 6 0%
- jit-lock-fontify-now 6 0%
+ funcall 6 0%
+ org-cycle-hide-archived-subtrees 2 0%
+ org-cycle-show-empty-lines 2 0%
+ show-children 34 2%
+ org-agenda 138 9%
+ previous-line 120 8%
+ byte-code 76 5%
+ find-file 31 2%
+ save-buffer 19 1%
+ org-shiftleft 15 1%
+ execute-extended-command 3 0%
+ org-shiftright 2 0%
- autoload-do-load 3 0%
i hope the format is ok.
Thanks so much
Am 16.01.2015 um 22:18 schrieb Nicolas Goaziou:
> Hello,
>
> Michael Ziems <sane@xiron.de> writes:
>
>> i got two windows machines: one is a surface with an i5 cpu and
>> a desktop machine with an amd 6 core cpu.
>>
>> on both machines i have org mode 8.2.10.
>>
>> when i switch the prioity in an 15k line org file having 614kbyte in
>> size on the i5 machine the system is really laggy and it takes up to
>> two seconds changing the priority of todo headlines. on the desktop
>> machine with a similar powerful cpu one a core level the changing is
>> lightning fast. recently i got get the i5 machine also that fast by
>> just adding the file again to the agenda list, but after restarting
>> emacs it was slow again and now i cannot reproduce the same.
>>
>> does anyone have an idea what could be the reason here?
> No idea, but you could do some profiling and report the results here.
> See `profiler-start'.
>
>
> Regards,
>
Michael Ziems <sane@xiron.de> writes:
> thanks for the reply. is this information already helpful:
>
> - command-execute 1331 92%
> - call-interactively 1327 91%
> - org-shiftdown 302 20%
> - call-interactively 302 20%
> - org-priority-down 302 20%
> org-priority 302 20%
> - org-shiftup 293 20%
> - call-interactively 293 20%
> - org-priority-up 293 20%
> org-priority 293 20%
> - next-line 183 12%
> - funcall 183 12%
> - #<compiled 0xc28a69> 183 12%
> - line-move 183 12%
> line-move-visual 180 12%
> - org-cycle 145 10%
> - org-cycle-internal-local 145 10%
> - run-hook-with-args 108 7%
> - org-optimize-window-after-visibility-change 104 7%
> - org-subtree-end-visible-p 8 0%
> - pos-visible-in-window-p 6 0%
> - jit-lock-function 6 0%
> - jit-lock-fontify-now 6 0%
> + funcall 6 0%
> + org-cycle-hide-archived-subtrees 2 0%
> + org-cycle-show-empty-lines 2 0%
> + show-children 34 2%
> + org-agenda 138 9%
> + previous-line 120 8%
> + byte-code 76 5%
> + find-file 31 2%
> + save-buffer 19 1%
> + org-shiftleft 15 1%
> + execute-extended-command 3 0%
> + org-shiftright 2 0%
> - autoload-do-load 3 0%
I don't see anything suspicious. Can you try using ELP (see
`elp-instrument-package') to instrument org package?
Regards,
Hello,
what actually is org mode doing during org-shiftdown and org-shiftup as
they are quite heavy with 302 in comparison to org-shiftleft with 15.
i tried elp-instrument-package but im not sure how to get data out of it.
thanks
Am 16.01.2015 um 22:44 schrieb Nicolas Goaziou:
> Michael Ziems <sane@xiron.de> writes:
>
>> thanks for the reply. is this information already helpful:
>>
>> - command-execute 1331 92%
>> - call-interactively 1327 91%
>> - org-shiftdown 302 20%
>> - call-interactively 302 20%
>> - org-priority-down 302 20%
>> org-priority 302 20%
>> - org-shiftup 293 20%
>> - call-interactively 293 20%
>> - org-priority-up 293 20%
>> org-priority 293 20%
>> - next-line 183 12%
>> - funcall 183 12%
>> - #<compiled 0xc28a69> 183 12%
>> - line-move 183 12%
>> line-move-visual 180 12%
>> - org-cycle 145 10%
>> - org-cycle-internal-local 145 10%
>> - run-hook-with-args 108 7%
>> - org-optimize-window-after-visibility-change 104 7%
>> - org-subtree-end-visible-p 8 0%
>> - pos-visible-in-window-p 6 0%
>> - jit-lock-function 6 0%
>> - jit-lock-fontify-now 6 0%
>> + funcall 6 0%
>> + org-cycle-hide-archived-subtrees 2 0%
>> + org-cycle-show-empty-lines 2 0%
>> + show-children 34 2%
>> + org-agenda 138 9%
>> + previous-line 120 8%
>> + byte-code 76 5%
>> + find-file 31 2%
>> + save-buffer 19 1%
>> + org-shiftleft 15 1%
>> + execute-extended-command 3 0%
>> + org-shiftright 2 0%
>> - autoload-do-load 3 0%
> I don't see anything suspicious. Can you try using ELP (see
> `elp-instrument-package') to instrument org package?
>
>
> Regards,
Michael Ziems <sane@xiron.de> writes: > what actually is org mode doing during org-shiftdown and org-shiftup > as they are quite heavy with 302 in comparison to org-shiftleft with > 15. 302 are spent on `org-priority'. Not sure which part is expensive. > i tried elp-instrument-package but im not sure how to get data out of > it. Call M-x elp-results It is better to run an uncompiled Org (C-u M-x org-reload) Regards,
Hello,
thanks for the really good help here. Here the results:
org-shiftdown
Call Count: 4
Elapsed time: 3.953
Average time: 0.98825
Am 17.01.2015 um 17:22 schrieb Nicolas Goaziou:
> Michael Ziems <sane@xiron.de> writes:
>
>> what actually is org mode doing during org-shiftdown and org-shiftup
>> as they are quite heavy with 302 in comparison to org-shiftleft with
>> 15.
> 302 are spent on `org-priority'. Not sure which part is expensive.
>
>> i tried elp-instrument-package but im not sure how to get data out of
>> it.
> Call M-x elp-results
>
> It is better to run an uncompiled Org (C-u M-x org-reload)
>
>
> Regards,
Michael Ziems <sane@xiron.de> writes:
> thanks for the really good help here. Here the results:
>
> org-shiftdown
> Call Count: 4
> Elapsed time: 3.953
> Average time: 0.98825
I would need the detailed results, i.e., the 10 top entries from the
results buffer.
Regards,