Re: Remote .vs Local IRIS Performer graphics

New Message Reply Date view Thread view Subject view Author view

Michael Jones (mtj++at++babar)
Fri, 29 Apr 1994 07:51:33 -0700


Lew sent the following note and then asked me to send it out
to the info-performer mailing list. How common is this type
of situation? Comments?

On Apr 29, 7:45am, Lew Hitchner wrote:
> Subject: Re: Remote .vs Local IRIS Performer graphics
:Mike Jones replied:
:
:> .
:> .
:> .
:> 9000 tris/frame ++at++ 30Hz => 270000 triangles/sec:
:> 270000 x 3 x 48 = 38.88 mbytes/sec (bus speeds)
:
:> 231 tris/frame ++at++ 30Hz => 6944 triangles/sec:
:> 6944 x 3 x 48 = 0.999936 mbytes/sec (ethernet speeds)
:
:> Do you want to drive a 231-polygon display from your Onyx?
:
:In my experience, and I would suspect also that of many Performer
:users, the example of driving a "231-polygon display" is probably
:common (or, alternatively a 2310-polygon display at 3 Hz). This would
:not be for production type results, but for development testing. I
:found that very frequently I wanted to try out something new just to
:see if "it works at all" and didn't care about frame rates or whether I
:tested it with a large database. Often the "does it work at all" test
:can be conducted with a toy database at low framerates. It's hard to
:estimate, but I would guess that perhaps as many as 50% of my test runs
:are in the "does it work" category and the rest require testing with
:large database at high frame rates. In environments where there's one
:"big" machine (e.g., 4 or 8 CPU Onyx) and many networked "small"
:machines (e.g., Indigos), developers usually develop and test on the
:small machines (single CPU) on their desktop. But, you also need to
:check out your latest development on the "big machine" with its OS,
:multi-CPU, and graphics hardware environment. But, in large
:organizations the console of "big machine" may not always be available
:on demand for every developer whenever he or she wants to test their
:latest "enhancement". This is the case at NASA Ames where the main
:SkyWriter often must be scheduled in advance for using it at the
:console in its lab but it's nearly always accessible over the network
:for quick shots at trivial tests (and then, of course, analysis of the
:core dump your test generated). Also, if you are running dbx or other
:CASE analysis tools remotely on the multi-CPU machine, network transfer
:rate is of little concern.
:
: Lew Hitchner
: VR consultant
: (formerly NASA Ames Res. Center)
>-- End of excerpt from Lew Hitchner

-- 

Be seeing you, Phone:415.390.1455 Fax:415.390.2658 M/S:8L-590 Michael T. Jones Silicon Graphics, Advanced Graphics Division mtj++at++sgi.com 2011 N. Shoreline Blvd., Mtn. View, CA 94039-7311


New Message Reply Date view Thread view Subject view Author view

This archive was generated by hypermail 2.0b2 on Mon Aug 10 1998 - 17:50:15 PDT

This message has been cleansed for anti-spam protection. Replace '++at++' in any mail addresses with the '@' symbol.