Notes 2/6/06

-Performance Comparison paper
Chromium better with gigabit switch, may have changed results
Using OpenSG for all tests may have been unfair
OpenSG built on top of OpenGL, Chromium replaces OpenGL
OpenSG replicates scene graph on every machine, Chromium does calculations at the beginning then distributes it
Why does VRJuggler perform about the same as OpenSG? Because VRJuggler was using OpenSG.
Can just use OpenGL and it will work with Chromium, don't need to learn something else.
May really be comparing [scene graph support in OpenSG] vs. [OpenGL]

-Where will all the pixels come from paper
DPI on printers and monitors aren't the same, really Big Bertha = printer resolution
Faster to redraw what changed than redrawing all pixels
A learning algorithm that knows where you put things would work well
Intelligent pixels, each pixel knows if it's changing... a lot of memory management
Could render directly in screen, if we eliminate wiring then we reduce 45 years to 10

Big Picture
Each pixel is a screen [network problem] vs. One big screen [memory/processing problem]
Wiring problems
-Is there some optimal sweet spot?
-Is all of this temporary? Will it all eventually be one machine and one screen?