Web Images Videos Maps News Shopping Google Mail more »
Recently Visited Groups | Help | Sign in
Google Groups Home
comp.lang.lisp
+ new post
About this group
Subscribe to this group
This is a Usenet group - learn more
Message from discussion Very poor Lisp performance
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Follow-up To:
Add Cc | Add Follow-up to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers that you hear
 
M Jared Finder  
View profile   Translate to Translated (View Original)
 More options 13 Aug 2005, 04:58
Newsgroups: comp.lang.lisp
From: M Jared Finder <ja...@hpalace.com>
Date: Fri, 12 Aug 2005 20:58:09 -0700
Local: Sat 13 Aug 2005 04:58
Subject: Re: Very poor Lisp performance
Reply to author | Forward | Print | View thread | Show original | Report this message | Find messages by this author

Jon Harrop wrote:
> Several people have kindly ported my ray tracer from this page:

>   http://www.ffconsultancy.com/free/ray_tracer/languages.html

> to Lisp. Some of them are reporting competitive performance. However, when I
> try to run their programs with either CMUCL or SBCL they are two orders of
> magnitude slower. Given the number of people claiming similarly good
> performance, I'd like to know what the possible cause of the relative
> slowdown on my computer is?

> My system is an unladen 900MHz Athlon T-bird with 768Mb RAM running Debian
> testing with SBCL 0.8.16 and CMUCL "19b-release-20050628-3 + minimal debian
> patches". Other people have both slower and faster CPUs and more and less
> RAM but all are consistently much faster than mine.

> I believe SBCL always compiles to native code and I am asking CMUCL to
> compile to native code with:

> (compile-file "ray4.lisp")
> (load "ray4.x86f")
> (time (main 6.0 "image.pgm" 256.0 4.0))

> Any ideas?

Post the ported code and we can take a look at it.  Without the code, we
can only make shots in the dark.

   -- MJF


    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message, you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Google Groups - Google Home - Terms of Service - Privacy Policy
©2009 Google