X me prenne moins que les 60 à 120 Mo d'occupation mémoire habituel ?
Q. Why does X use so much memory?
A. When measuring any application's memory usage, you must be careful to distinguish between physical system RAM used and virtual mappings of shared resources. For example, most shared libraries exist only once in physical memory but are mapped into multiple processes. This memory should only be counted once when computing total memory usage. In the same way, the video memory on a graphics card or register memory on any device can be mapped into multiple processes. These mappings do not consume normal system RAM.
The 'pmap' utility described in the above thread is available here: http://web.hexapodia.org/~adi/pmap.c and is a useful tool in distinguishing between types of memory mappings. For example, while 'top' may indicate that X is using several hundred MB of memory, the last line of output from pmap: mapped: 287020 KB writable/private: 9932 KB shared: 264656 KB
reveals that X is really only using roughly 10MB of system RAM (the "writable/private" value).
RESUME FRANCOPHONE:
En clair, ne te fie pas a top. top indique une consommation memoire fausse pour X car elle compte aussi celle des bibliotheques partagees (par X avec d'autres programmes). Et y'a pas que ca. Utilise pmap [pid de X] pour voir la consommation exacte de X. pmap est maintenant installe sur beaucoup de systemes. Note que c'est valable pour tout programme.
"La liberté est à l'homme ce que les ailes sont à l'oiseau" Jean-Pierre Rosnay
[^] # Re: Cher Père Noël...
Posté par ZeroHeure . En réponse à la dépêche X11R7.0 sous le sapin de Noël. Évalué à 7.
Q. Why does X use so much memory?
A. When measuring any application's memory usage, you must be careful to distinguish between physical system RAM used and virtual mappings of shared resources. For example, most shared libraries exist only once in physical memory but are mapped into multiple processes. This memory should only be counted once when computing total memory usage. In the same way, the video memory on a graphics card or register memory on any device can be mapped into multiple processes. These mappings do not consume normal system RAM.
This has been a frequently discussed topic on XFree86 mailing lists; see, for example: http://marc.theaimsgroup.com/?l=xfree-xpert&m=9683576711(...)
The 'pmap' utility described in the above thread is available here: http://web.hexapodia.org/~adi/pmap.c and is a useful tool in distinguishing between types of memory mappings. For example, while 'top' may indicate that X is using several hundred MB of memory, the last line of output from pmap:
mapped: 287020 KB writable/private: 9932 KB shared: 264656 KB
reveals that X is really only using roughly 10MB of system RAM (the "writable/private" value).
RESUME FRANCOPHONE:
En clair, ne te fie pas a top. top indique une consommation memoire fausse pour X car elle compte aussi celle des bibliotheques partagees (par X avec d'autres programmes). Et y'a pas que ca. Utilise pmap [pid de X] pour voir la consommation exacte de X. pmap est maintenant installe sur beaucoup de systemes. Note que c'est valable pour tout programme.
"La liberté est à l'homme ce que les ailes sont à l'oiseau" Jean-Pierre Rosnay