🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.lang.postscript
Article #1370

benchmarking postscript processors

#1370
From: Chaim Bendelac
Date: Sun, 26 Nov 1989 07:00
13 lines
1095 bytes
Is there a "standard" and reasonably repeatable way to measure the
real performance of a postscript processor? Are there any "standard"
(public-domain) benchmark used for this purpose? (I know about the
"blue book" and other standard graphic examples, but they do not make
any claim of being "representative" of real usage, as whetstones and 
dhrystones try to be, in the scientific world).
How is performance measured? Stopwatch including page-eject? "usertime"?
Are pages separated by "quit"s? How does the usertime encapsulation
ensures objectivity? How do you separate I/O from processing from imaging
from printing times? How are caching and other "system" parameters isolated?

Anyone with some knowledge on postscript benchmarking care to expand?
Thanks!
Technical Details
Message-ID: <13436@nsc.nsc.com>
Path: arc1-ca.pugleaf.net!utzoo!attcan!uunet!mailrus!purdue!decwrl!ucbvax!hplabs!nsc!chaim

Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!attcan!uunet!mailrus!purdue!decwrl!ucbvax!hplabs!nsc!chaim
From: chaim@nsc.nsc.com (Chaim Bendelac)
Newsgroups: comp.lang.postscript
Subject: benchmarking postscript processors
Message-ID: <13436@nsc.nsc.com>
Date: 26 Nov 89 07:00:14 GMT
Organization: National Semiconductor, Santa Clara
Lines: 13