🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.lang.prolog
Article #1298

Benchmark Programs

#1298
From: Micha Meier
Date: Sat, 20 Oct 1990 21:23
52 lines
3085 bytes
Some time ago, I've posted a request for large benchmark programs.
Although I did not expect any overwhelming response, the result
can be considered as rather poor. So here I am again: please,
if you have any nontrivial, long programs, make them available
to the benchmark suite. In this way, you help the whole Prolog
community, because the more programs we have, the better we can
find out what programs the people are actually writing and
concentrate on how to make these programs run faster. The usual
purpose of benchmark programs, namely comparing the efficiency
of different systems, is also important, but not that
much. More important is that the implementors can make
a reasonable statistics of what features the real-life programs have,
and then to decide which of them are worth to speed up
to make the whole program run faster.

I've learned that some people are afraid to make their programs
available because they think that their programs are not written
in a good style and they are also afraid of R.A.O'Keefe's comments.
Such worries are completely unnecessary. On the contrary - if
all the programs were perfect, a benchmark suite made out of them
would not be as significant as a real-life one.
The fun with Prolog is that it is not that difficult
(well, not as difficult as in some other languages) to
take an inefficient Program, process it, and obtain
an efficient one. To do this, one of course needs a lot
of inefficient programs to practice with them.
(As a matter of fact, buggy programs are very important
as well - how else can we write good debuggers
if we work always with mistyped append or similar programs?)
The same thing concerns e.g. the cuts. A lot of people
put too many cuts into their programs and are then
reluctant to show them to the public, but how can we
write tools which remove these cuts automatically if we don't have enough
programs overloaded with cuts?

Prolog has not a very good reputation in the CS field
(I was actually quite surprized when I found out at the last
IFIP Congress that very few of the people there take Prolog seriously),
one reason for that is certainly its slowness.
Please, if you believe in Prolog, help us to make it better,
we need your programs, be it good or bad. The main thing
is that they are being used for something significant.
You can do so anonymously, if you prefer, or with full copyright,
it does not matter. All you have to do is to let me know where
your program is accessible.

--Micha Meier
--
USA     micha%ecrc.de@pyramid.com	MAIL	Micha Meier
						ECRC, Arabellastr. 17
EUROPE  micha@ecrc.de				8000 Munich 81
						West Germany
Technical Details
Message-ID: <1744@ecrc.de>
Path: arc1-ca.pugleaf.net!utzoo!attcan!uunet!van-bc!ubc-cs!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!emory!sol.ctr.columbia.edu!ira.uka.de!fauern!tumuc!guug!ecrc!micha

Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!attcan!uunet!van-bc!ubc-cs!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!emory!sol.ctr.columbia.edu!ira.uka.de!fauern!tumuc!guug!ecrc!micha
From: micha@ecrc.de (Micha Meier)
Newsgroups: comp.lang.prolog
Subject: Benchmark Programs
Message-ID: <1744@ecrc.de>
Date: 20 Oct 90 21:23:51 GMT
Sender: news@ecrc.de
Reply-To: micha@ecrc.de (Micha Meier)
Organization: ECRC
Lines: 52