Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!cs.utexas.edu!uunet!orca!undies!pmartz
From: pmartz@undies.dsd.es.com (Paul Martz)
Newsgroups: comp.sys.sgi
Subject: lines and libraries
Message-ID: <1991Apr17.144853.17441@dsd.es.com>
Date: 17 Apr 91 14:48:53 GMT
Sender: usenet@dsd.es.com
Reply-To: pmartz@undies.dsd.es.com (Paul Martz)
Organization: Evans & Sutherland Computer Corp., Salt Lake City, UT
Lines: 22
Nntp-Posting-Host: 130.187.85.56

I have been developing some code on a Personal Iris GT which draws
primarily vectors. Using the v3f function, I was getting about 135K
vecs/sec, so I tried move/draw instead and started getting about 165K
vecs/sec. From this I deduced that move/draw is optimized for the
Personal Iris.

Then I sent the compiled executable to a friend who has a VGX. He
wrote back that vector performance was the worst he'd ever seen: 155K
vecs/sec! (Still using move/draw.)

So I have two questions:

1) Is it normal to see move/draw perform better on a Personal Iris GT
than a VGX? I really should be using v3f for VGX machines, right?

2) Is the libgl_s.a library shipped with a Personal Iris different
from what's shipped with a VGX? I.e., could I have my friend
recompile/relink on the VGX and get different results?
-- 

   -paul	pmartz@dsd.es.com
		Evans & Sutherland