Weiblen, Mike (mweiblen++at++wb.com)
27 Jun 1994 11:28:04 U
===============================================================================
I'm doing stress experiments to determine what limits the amount of texture I
can load into RAM.
The system I'm experimenting with is a 4-proc ONYX, 512MB RAM, 2 RM5s. My
tests consist of loading many of our hi-res NELLIS geospecific photo textured
terrain tiles (3.7MB of texture memory each).
My initial experiments ended with "ERROR #2 texdef2d: ERR_OUTMEM" after
Performer pfuDownloadTexList() reports ~114MB of texture loaded.
I then set my filesize, datasize, stacksize, memoryuse and vmemoryuse limits to
"unlimited". I watch the memory consumption with gr_osview and Performer's
output as the RMs texdef() and page out the textures.
gr_osview's memory bargraph goes up to 128M of some unspecified unit (words?).
When it gets to ~122M, I see disk activity which bumps it down to ~118M. At
the time of the first disk swap, pfuDownloadTexList() is reporting about 250MB
texture loaded.
Paging from the RM to RAM is bad enough, but swapping to disk is a real killer,
and I'm looking for what kind of control I have over the texture swap
threshold.
Is there a manifest limit on the total RAM texture capacity? It has been
difficult for me to get time on our 1500MB ONYX to test if the limit is a
percentage of total mem. The bottom line: On the big ONYX, will it be
possible for me to load our entire hi-res NELLIS database (total 525 MB of
texture) without swapping textures to disk?
-- mew
This archive was generated by hypermail 2.0b2 on Mon Aug 10 1998 - 17:50:21 PDT