NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
Hi Igor, > in the attached example some points are added to a display without a > FunctionType and a FlatField. > How many points can VisAD handle in this way? What happens when it > reaches the limit? There are no hard limits in VisAD. Each distinct DataReference linked to a DisplayImpl adds several new objects, so after a while you'll run out of memory and your application will slow down. You'll have to discover the practical limits for your application by experimenting. But JDK 1.4 will support 64-bit addressing, and chips will continue getting faster according to Moore's law for at least 20 more years. So eventually you'll be able to display much more data than your eye can see, without running into any limits in VisAD. And VisAD's pervasive use of RMI distributed objects is enabling it to be used for all kinds of experiments with distributed computing for dealing with large amounts of data. Cheers, Bill ---------------------------------------------------------- Bill Hibbard, SSEC, 1225 W. Dayton St., Madison, WI 53706 hibbard@xxxxxxxxxxxxxxxxx 608-263-4427 fax: 608-263-6738 http://www.ssec.wisc.edu/~billh/vis.html
visad archives: