Re: Structure of large link libraries in f95
- From: Jan Vorbrüggen <jvorbrueggen-not@xxxxxxxxxxx>
- Date: Thu, 30 Mar 2006 16:30:04 +0200
Besides the simple size of the executable on disk, you may wonder
about memory space while the program is running. Again, don't worry
about it. Modern virtual memory systems only 'page in' portions of
the code, as needed, so wasting a lot of time worrying about it
is again somewhat fruitless in reality.
That doesn't jive with my reality. I spend minutes each day on a laptop
with 512 MBytes of memory waiting for the stupid Windoze paging system to
page in those bloatware applications. That's even true for Thunderbird and
Firefox, which are relatively light weight - "only" 56 MB and 7 MB, respec-
tively. Of course, the enormous sizes of those MS Office files that swamp
the file system cache contribute to this.
Jan
.
- Follow-Ups:
- Re: Structure of large link libraries in f95
- From: Gordon Sande
- Re: Structure of large link libraries in f95
- From: Walter Spector
- Re: Structure of large link libraries in f95
- References:
- Structure of large link libraries in f95
- From: Charles Russell
- Re: Structure of large link libraries in f95
- From: robert . corbett
- Re: Structure of large link libraries in f95
- From: Charles Russell
- Re: Structure of large link libraries in f95
- From: Walter Spector
- Structure of large link libraries in f95
- Prev by Date: Re: How to link a Fortran static library to a C++ program?
- Next by Date: Re: How to link a Fortran static library to a C++ program?
- Previous by thread: Re: Structure of large link libraries in f95
- Next by thread: Re: Structure of large link libraries in f95
- Index(es):
Relevant Pages
|
|