byte-accuracy red, green, blue channels) = 27 bytes. More likely 28 bytes as colours are probably stored as 32-bit integers, allowing for an unused alpha channel.
28 * 800,000 equals roughly 22 megabytes, which is way down from 9 gigabytes. That's a 400 fold memory overhead, which is pretty hefty.
Grasshopper stores points as instances of classes, so on 64-bit systems it actually takes 64+64+3*8 = 152 bytes per point*, which adds up to 122MB, still way less than 9GB. It would be interesting to know where all the memory goes...
* Grasshopper points also store reference data, in case they come from the Rhino document. This data will not exist, but even so it will require 64-bits of storage.…
Added by David Rutten at 4:13pm on December 11, 2014
an A,B & C input that relates to vertex indices. If had a 1 dimensional point grid (as you do) with 10 U and 10 V, the A,B,C input needs to have a list pattern of '3 index value' paths (e.g.) {0,1,10},{1,11,10},{1,2,11}...
definition showing a 3 count point list, 1 face, 1 mesh object.…