unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Alex Bennee <kernel-hacker@bennee.com>
To: Peter Dyballa <Peter_Dyballa@web.de>
Cc: help-gnu-emacs mailing list <help-gnu-emacs@gnu.org>
Subject: Re: Tracking down why emacsclient -c is so slow
Date: Sat, 22 Aug 2009 09:10:33 +0100	[thread overview]
Message-ID: <b2cdc9f30908220110t7ef70f0yb4f4bf87ec04946c@mail.gmail.com> (raw)
In-Reply-To: <399CF4B9-9CAD-4E68-BB8F-09EF6A787E43@Web.DE>

2009/8/21 Peter Dyballa <Peter_Dyballa@web.de>:
>
> Am 21.08.2009 um 20:25 schrieb Alex Bennee:
>
>> Are there any other hooks run between after-make-frame-functions and
>> server-visit-hook I can hook to to see why it takes so long?
>
>
> Yes, they're called PCI, PCI-Express, AGP, and much more. Stick another and
> faster graphics card in such a slot and you'll less consumed to create a new
> frame.
>

The current delays I'm seeing are a little excessive, especially
considering that the rest of the OS doesn't seem to have too much
problem displaying compiz and full-rate HD video.

The results of the profile look like:

Function Name                    Call Count  Elapsed Time  Average Time
===============================  ==========  ============  ============
make-frame                       2           17.385781     8.6928905
frame-set-background-mode        14          0.0370519999  0.0026465714
frame-parameters                 54          0.0008449999  1.564...e-05
frame-parameter                  494         0.0007000000  1.417...e-06
framep                           956         0.0004720000  4.937...e-07
frame-list                       429         0.0003700000  8.624...e-07
frame-or-buffer-changed-p        39          0.0001459999  3.743...e-06
framep-on-display                202         0.0001409999  6.980...e-07
frame-selected-window            46          5.799...e-05  1.260...e-06
frame-live-p                     58          4.599...e-05  7.931...e-07
frame-visible-p                  53          2.800...e-05  5.283...e-07
frame-char-width                 13          1.200...e-05  9.230...e-07
frame-char-height                14          1.199...e-05  8.571...e-07

I thought I'd throw oprofile at the task but as far as it's concerned
emacs spends most of it's time in mark-object and Fbyte_code and isn't
actually a significant proportion of the CPU time. Something else
seems to be going on.

-- 
Alex, homepage: http://www.bennee.com/~alex/
http://www.half-llama.co.uk




  reply	other threads:[~2009-08-22  8:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-21 18:25 Tracking down why emacsclient -c is so slow Alex Bennee
2009-08-21 18:54 ` Peter Dyballa
2009-08-22  8:10   ` Alex Bennee [this message]
2009-08-22 10:35     ` Peter Dyballa
2009-08-22 11:33       ` Alex Bennee
2009-08-22 11:58         ` Peter Dyballa
2009-08-22 12:47           ` Alex Bennee
2009-08-22 14:03           ` Alex Bennee
2009-08-22 14:26             ` Alex Bennee
     [not found]   ` <mailman.5119.1250928641.2239.help-gnu-emacs@gnu.org>
2009-08-22  9:53     ` A.Politz
2009-08-22 11:27       ` Alex Bennee

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.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=b2cdc9f30908220110t7ef70f0yb4f4bf87ec04946c@mail.gmail.com \
    --to=kernel-hacker@bennee.com \
    --cc=Peter_Dyballa@web.de \
    --cc=help-gnu-emacs@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.
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).