Path: utzoo!yunexus!ists!helios.physics.utoronto.ca!news-server.csri.toronto.edu!utgpu!cunews!bcars8!bnrgate!bcars85!jsparkes From: jsparkes@bcars85.bnr.ca (Jeff Sparkes) Newsgroups: comp.windows.x Subject: window manager traffic Message-ID: Date: 29 May 90 12:42:49 GMT Article-I.D.: bcars85.jsparkes.643984969 Sender: news@bnrgate.bnr.ca (USENET News Administration) Distribution: comp Organization: Bell-Northern Research, Ltd. Ottawa Ontario CANADA Lines: 20 I've been doing some measurements of packets from my NCD X terminal. Various window managers seem to generate enormous amounts of traffic for common operations. Popping up a menu or placing a window causes the NCD to generate packtes as fast as it can, about 300 packets/s. I realize that this comes from X's workstation heritage, where WM traffic was just memory copies. Does anyone know how to (or plan to) reduce this traffic? On our large network, it's possible for WM traffic to take up a large chunk of network bandwidth. DEC may have done the right with their new X terminal by putting the WM in the server. Do any other manufacturers (especially NCD) plan to do this? It would probably be better to have multiple loadable WM's, but I'm sure we could live with a single hardcoded one. -- Jeff Sparkes jsparkes@bnr.ca Cat: Is that what I think it is? Lister: What do you think it is? Cat: A big orange whirly thing in space!