Subject: Re: Slow X applications [was Re: X server as a Unix system process]
To: Ken Hornstein <email@example.com>
From: Jukka Marin <firstname.lastname@example.org>
Date: 07/29/1997 14:11:01
On Mon, Jul 28, 1997 at 02:33:04PM -0400, Ken Hornstein wrote:
> >> Later, Jukka reported that running his application with an X server
> >> that does not use mmap/munmap, made things go much faster. I suspect
> >> that the application is still doing small writes, but the round-trip
> >> time between the application and the X-server is now low enough
> >> that the small packet size is masked.
> >Yes, I believe this is the case.
> I don't think that is the case. The real problem (as I saw it) was that
> the mmap allocator was just taking a long time to run. The fact that
> it was allocating memory for _every request_ is actually a bit crazy.
Well, let's compromise: The poor performance is caused _both_ by the
small packets sent to the X server _and_ the slow memory allocation and
deallocation times. I would like both problems fixed - if we knew where
the real problems were. I don't know why the X clients use such small
packets or commands.. and I don't know why the X server eats so much
time allocating and deallocating memory. I'm 50% happy with the newly
built X server (can run Applixware again), but it would be nice if there
was a real solution, too.. :)