unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: storm@cua.dk (Kim F. Storm)
Cc: levoy@cs.stanford.edu, gerd@gnu.org, emacs-devel@gnu.org
Subject: Re: [levoy@cs.stanford.edu: Poor performance over DSL link]
Date: 12 Sep 2002 00:38:06 +0200	[thread overview]
Message-ID: <5x7khsp2y9.fsf@kfs2.cua.dk> (raw)
In-Reply-To: <200209112003.g8BK3ph20627@wijiji.santafe.edu>

Richard Stallman <rms@gnu.org> writes:

>     But there were still several areas which could be improved - but it
>     would be non-trivial to do so, either because X-servers have different
>     capabilities, or because the "excessive" traffic was partially caused
>     by some of the X-library functions.  
> 
> What areas are they?  Maybe someone else would like to work on it.
> At very least we can put them in etc/TODO.

It's been a long time, but I used Ethereal to trace the X traffic, and it
was quite obvious that the same sequences of events were repeated over
and over again...

IIRC, it had to do with allocating colors (or pixels?) in the X
server, updating [tiny parts of the display], and then deallocating
the colors - and doing that over and over for every tiny update.

I discussed ways to cache this information with Gerd, but it was
non-trivial because different X-servers had different number of
available colors/pixels, so it seemed to be difficult to do in a
general way.

> 
>     I'm afraid I no longer have the correspondance with Gerd and Richard
>     on this issue; any chance that either of you still have a copy [I think
>     my email address at the time was stormware@get2net.dk] ?
> 
> If I received the messages, I still have them.  What time period should
> I search?

Try January/February 2001 

-- 
Kim F. Storm <storm@cua.dk> http://www.cua.dk

  reply	other threads:[~2002-09-11 22:38 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-09  0:21 [levoy@cs.stanford.edu: Poor performance over DSL link] Richard Stallman
2002-09-09 10:04 ` Kim F. Storm
2002-09-09  9:12   ` Marc Levoy
2002-09-09 10:34     ` Kim F. Storm
2002-09-09 23:33     ` Richard Stallman
2002-09-10 23:56       ` Kim F. Storm
2002-09-11 20:03         ` Richard Stallman
2002-09-11 22:38           ` Kim F. Storm [this message]
2002-09-12 16:41             ` Richard Stallman
2002-09-12 16:41             ` Richard Stallman
     [not found]               ` <5xhegunctj.fsf@kfs2.cua.dk>
2002-09-14 17:35                 ` Richard Stallman
     [not found]       ` <15741.13832.457353.277778@dda.Stanford.EDU>
2002-09-11  1:40         ` Richard Stallman
2002-09-11  9:04           ` Gerd Moellmann
2002-09-09 23:33   ` Richard Stallman
2002-09-10 23:34     ` Kim F. Storm
2002-09-11  1:15       ` Miles Bader
     [not found]         ` <5xr8g0pcpv.fsf@kfs2.cua.dk>
2002-09-12  1:20           ` Miles Bader
2002-09-11 20:03       ` Richard Stallman

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=5x7khsp2y9.fsf@kfs2.cua.dk \
    --to=storm@cua.dk \
    --cc=emacs-devel@gnu.org \
    --cc=gerd@gnu.org \
    --cc=levoy@cs.stanford.edu \
    /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.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).