Volume rendering seems to use more memory than necessary. It prohibits the application to work on very large data sets.
Details:
Test data set: a 1024 cubed regular grid data in 32-bit floating point.(/little_glade/shaomeng/vorticity/wx.vdc, /glade/p/cisl/vast/vapor/Bugs/vorticity/wx.vdc). Notice it has only one time step with only one variable.
This grid itself is 4.29 GB.
During volume rendering, VAPOR takes 18 GB memory. That's about 4.2X of the grid size.
This means a commonly seen 16GB memory desktop cannot analyze a 4GB data set, and a 1TB memory HPC cannot analyze a 256GB data set.
Volume rendering seems to use more memory than necessary. It prohibits the application to work on very large data sets.
Details:
1024
cubed regular grid data in 32-bit floating point.(/little_glade/shaomeng/vorticity/wx.vdc
,/glade/p/cisl/vast/vapor/Bugs/vorticity/wx.vdc
). Notice it has only one time step with only one variable.4.2X
of the grid size.