X takes up 188 MB of memory
I'm using the nvidia driver (version 1.0.2314) on the student PC's running Red Hat 7.3 at the university where I work.
When X is started, before I even log in, X uses 188 MB of memory. That is a bit too much, when the machines have only 256 MB RAM... On my colleagues PC he runs the standard Red Hat driver, and his X uses "only" 120 MB of RAM. That means that the Nvidia driver uses 68 MB more than the standard one.
My question is, is the nvidia driver supposed to take up that much memory?
I know I'm not using the newest version, but I imagine a newer one will just take up even more memory?
The Graphichs card I use is some Nvidia GeForce 2 thing, 2-3 years old.
It is normal that X uses that much memory. In that amount of memory are X apps and so on included too. Try to use a newer driver version perhaps a newer version fixes some "problems".
Well i HAVE to speak to this point :)
First of all, if there is NOTHING running on a regular Xserver, there really should be not much memory being used, BUT if your using nvidia's drivers, than you will realize that it still uses a ton of resources. Nvidia's drivers aren't written to be extermely clean, as the xfree86 drivers are, Nvidia's drivers are written to be extremely fast.
I've seen this behaviour. Are you assessing size using 'top'? top was reporting my X server to be using 256MB of memory on a box with 128MB RAM + 128MB swap. The fact that the box worked quite normally suggested that the numbers weren't quite right somehow.
It's not clear to me that this is actual, used, physical memory. I wonder if it might be a shared-memory segment, or something.
Do not be frightened of big values in 'top' or 'ps'. These programs shows memory segment sizes associated with given process, neither the physical memory usage nor "common" virtual memory (physical + swap). Just nvidia driver uses device memory mapping (mmap("/dev/nvidia0",..) into process memory space) and uncommitted SysV IPC shared memory. Most of this memory are "pure virtual", i.e. does not associated with physical pages, but part of them are associated with AGP memory.
PID USER PRI NI SIZE RSS SHARE STAT %CPU %MEM TIME COMMAND
2349 root 9 0 304M 15M 4824 S 0,0 6,2 8721m X
try to run cat /proc/2349/status (where 2349 is my PID of X, replace it by your own):
VmSize: 329020 kB
VmLck: 4294922036 kB
VmRSS: 15956 kB
VmData: 44248 kB
VmStk: 464 kB
VmExe: 1468 kB
VmLib: 4976 kB
We can see that X uses only 15MB of physical memory (RSS - Resident Set Size) and 44248 +464+1468+4976 (i.e. ~50MB) of "common" virtual memory (so ~35 MB in swap), where 5,5MB (VmExe and VmLib) can be shared (possibly) with another processes (another
copies of X for VmExe and another processes using the same shared libraries for VmLib).
As a couple have said it's not likely to be a big problem.
The mapped memory can be seen by doing
$ cat /proc/`pidof X`/maps
You'll see, amongst other things (like libc, libGL and other libraries), the driver will map the graphics card ram, agp space and registers.
|All times are GMT -5. The time now is 02:30 PM.|
Powered by vBulletin® Version 3.7.1
Copyright ©2000 - 2015, Jelsoft Enterprises Ltd.
Copyright ©1998 - 2014, nV News.