So I guess I don't know how much dx is using of your 4 GB, but when
you get screen subdivision failings--that usually indicates that the
renderer is trying to render too much information (I also have had
this happen when trying to render huge images). There is no reason to
pass such huge amounts of data to the renderer since there are a
limited number of pixels that can be used to display. For example--if
you have a 640x480 image window, try to keep the amount of data to be
rendered under 5-6MB. Anything above that and you will not be able to
discern the differences. So if you are sending the renderer things
that are say 500MB data objects, then you need to reduce their sizes
somehow (SimplifySurface, Speedy Glyphs, Reduce). There are other
techniques that can be helpful as well--and we are always available
for tech support at VIS, Inc.
David
Actually, I expect 4GB should be enough. However...
Even with 4GB on NetBSD there are a couple of data files I can't open
on my OpenDX *.net. Somebody said something about the per-process limit.
I get this...among others...
ERROR: Image: Display: Out of memory: Screen subdivision failed
I reset the server and get the same again. The NetBSD gurus said I might
look into sysctl. So...
From "man sysctl" I find I have like so...
<snip>
NetBSD 1.6.2_RC3 June 6, 1993 6
baal: {5} sysctl proc
proc.curproc.corename = %n.core
proc.curproc.rlimit.cputime.soft = unlimited
proc.curproc.rlimit.cputime.hard = unlimited
proc.curproc.rlimit.filesize.soft = unlimited
proc.curproc.rlimit.filesize.hard = unlimited
proc.curproc.rlimit.datasize.soft = 134217728
proc.curproc.rlimit.datasize.hard = 1073741824
proc.curproc.rlimit.stacksize.soft = 2097152
proc.curproc.rlimit.stacksize.hard = 33554432
proc.curproc.rlimit.coredumpsize.soft = unlimited
proc.curproc.rlimit.coredumpsize.hard = unlimited
proc.curproc.rlimit.memoryuse.soft = 3744112640
proc.curproc.rlimit.memoryuse.hard = 3744112640
proc.curproc.rlimit.memorylocked.soft = 1248037546
proc.curproc.rlimit.memorylocked.hard = 3744112640
proc.curproc.rlimit.maxproc.soft = 160
proc.curproc.rlimit.maxproc.hard = 532
proc.curproc.rlimit.descriptors.soft = 64
proc.curproc.rlimit.descriptors.hard = 1772
baal: {6}
</snip>
Which, if any of the above should I tamper with to let OpenDX take fuller
advantage of my new glut of RAM? Or do the DX gurus opine that I had ought
to rebuild my kernel? And if so, what ought I change?
TIA,
Gan
--
Mistera Sturno - Rarest Extinct Bird
<(+)__ Gan Uesli Starling
((__/)=- Kalamazoo, MI, USA
`||`
++ http://starling.us
--
.............................................................................
David L. Thompson Visualization and Imagery Solutions, Inc.
mailto:[EMAIL PROTECTED] 5515 Skyway Drive, Missoula, MT 59804
Phone : (406)756-7472
