|Cray-2 Fast Memory email@example.com (1993-05-13)|
|Re: Cray-2 Fast Memory firstname.lastname@example.org (1993-05-14)|
|Re: Cray-2 Fast Memory email@example.com (1993-05-26)|
|Re: Cray-2 Fast Memory firstname.lastname@example.org (1993-05-26)|
|Re: Cray-2 Fast Memory email@example.com (1993-05-27)|
|Re: Cray-2 Fast Memory firstname.lastname@example.org (1993-05-31)|
|From:||email@example.com (James A. Crotinger)|
|Organization:||Magnetic Fusion Energy - LLNL|
|Date:||Mon, 31 May 1993 06:15:02 GMT|
firstname.lastname@example.org (David desJardins) writes:
> We have never had a real problem with running out of local memory (and I
> have never heard of anyone using the paging option), but then our workload
> generally consists of relatively small codes, a few thousand lines
> perhaps, rather than several-hundred-thousand-line behemoths.
We have several codes on the NERSC Cray 2's that are always running
out of local memory. These codes employ a sophisticated runtime system
that provides an interpreter that has access to compiled variables and
subroutines. All of our stuff is compiled with -eP (the paging options)
but apparently some of the commercial libraries we link with are not.
This has gotten to be a real pain!
James A. Crotinger Lawrence Livermore N'Lab
email@example.com P.O. Box 808; L-630
(510) 422-0259 Livermore CA 94550
Return to the
Search the comp.compilers archives again.