| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 796.1 | Sounds like you've got a shortage of off-screen memory | 4205::HERBERT | Now at LKG - DTN 226-5995 | Wed May 17 1989 12:48 | 7 |
| It sounds like your offscreen memory is becoming badly fragmented; I suspect
that the applications that you are running allocate very large pixmaps, causing
the server to need to swap stuff between the GPX offscreen memory and main
memory.
Kevin
|
| 796.2 | background pixmap? | 8568::kittell | Richard S. Kittell - Database Sys | Wed May 17 1989 13:46 | 4 |
| I've also seen this occur when I put a picture in my background.
I stopped running phoon because of the terrible background
repaint performance.
|
| 796.3 | | RAB::DESAI | Jatin Desai | Wed May 17 1989 13:54 | 6 |
|
I too stopped having a pretty background because of this. The offednig
applications in my case were DECpaint, DECchart and DECwrite.
Jatin
|
| 796.4 | Paint it gray | 10388::CRAIG | XOFF EXXON! | Wed May 17 1989 16:12 | 6 |
|
I've noticed it too, with just DECterm windows and an XPHOON
background (on a 6MB VS2000). Only on grayscale, though; it doesn't
manifest itself on a monochrome system.
|
| 796.5 | GPX only... and of course, XPHOON will be a major offender | 4205::HERBERT | Now at LKG - DTN 226-5995 | Wed May 17 1989 19:57 | 9 |
| XPHOON creates a pixmap as big as the entire screen, which uses � of the
total available offscreen memory. I'm pretty sure that DECterm will also
allocate somewhat large pixmaps when you start using REGIS.
All of this applies only to GPX systems; MFB systems don't have any off-screen
memory at all, so there is never any overhead of moving things back and forth.
Kevin
|
| 796.6 | Brings to mind a few questions concerning off-screen memory | 32423::SCHNEIDER | New lamps for old | Thu May 25 1989 17:00 | 11 |
| >All of this applies only to GPX systems; MFB systems don't have any off-screen
>memory at all, so there is never any overhead of moving things back and forth.
>
>Kevin
How much offscreen memory does a GPX have? Does it differ between the
different w/s's? What's MFB stand for and how do those systems store
pixmaps?
Dan
|
| 796.7 | GPX vs. MFB basics | 4205::HERBERT | Wasted daze; wasted knights | Fri May 26 1989 11:19 | 17 |
| I'm not sure exactly how much off-screen memory the GPX has, but I think I
recall hearing that it is about twice as much memory as the on-screen memory.
GPX systems include drawing hardware; the host CPU makes high-level requests
to the graphics processor (such as draw me a rectangle), and the GPX processor
takes care of it. The GPX hardware is capable of drawing into either the
on-screen or off-screen memory. Since pixmaps are objects which can be drawn
on by the GPX hardware, they must be in off-screen memory.
MFB stands for monochrome frame buffer. On MFB systems, there is no hardware
graphics assist; all graphics drawing is accomplished by the host CPU setting
appropriate pixels in the graphics memory. Since the host CPU is doing the
drawing, a pixmap gets stored in host memory (as part of the server's virtual
address space). So, on MFB systems, you have as much memory for pixmaps as
the server has available.
Kevin
|