Article View: comp.lang.misc
Article #4313Re: Relative Speed of Perl vs. Tcl vs. C
From: Eric Vought
Date: Thu, 01 Feb 1996 22:32
Date: Thu, 01 Feb 1996 22:32
26 lines
1944 bytes
1944 bytes
Reply To: adfh@village.ios.com > > Super-mini's (Convex amoung others) often have specialized vector and matrix > hardware that allow it to perform the same operation on large portions of > the vector with a single instruction cycle. This requires specialized > optimizing compilers. PERL wouldn't take advantage of the specialized > hardware/instruction set and thus would have a worse benchmark. > > My guess is that the generic term "modern RISC machines" is probably wrong. > Tom's original claim was probably for a UNIX desktop box and would > still hold true. The other issue, is : Is the Perl code readable? (then again, is *any* perl code readable?) If he has to hand optimize and obfuscate the code, where a C programmer can write code that is a) clear, and b) effectively optimized by the compiler, then perl is still significantly slower where the same amount of coding effort is applied. Secondly, is the C code being compared compiled with optimization? Is the executable stripped? I've noticed before that stripping and optimizing some programs can make a greater than e times difference by itself. If the C code is already e times faster, the difference becomes appreciable, especially if a difference of 2e can be obtained without any hand optimization effort.
Technical Details
Message-ID:
<Pine.LNX.3.91.960201172440.2697A-100000@localhost>Path:
arc1-ca.pugleaf.net!thea.dynanet.com!localhost!ewokReferences:
<4e3a2u$eoa@wcap.centerline.com> <4e54vc$7sk@orac.mon.rnb.com> <4elgpf$fgp@philabs.research.philips.com>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!thea.dynanet.com!localhost!ewok From: Eric Vought <ewok@localhost> Newsgroups: comp.lang.misc,comp.lang.perl.misc,comp.lang.tcl,comp.lang.c,comp.lang.java Subject: Re: Relative Speed of Perl vs. Tcl vs. C Date: Thu, 1 Feb 1996 17:32:31 -0500 Organization: DynaNet, Inc. Message-ID: <Pine.LNX.3.91.960201172440.2697A-100000@localhost> References: <4e3a2u$eoa@wcap.centerline.com> <4e54vc$7sk@orac.mon.rnb.com> <4elgpf$fgp@philabs.research.philips.com> NNTP-Posting-Host: village.ios.com Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII In-Reply-To: <4elgpf$fgp@philabs.research.philips.com>