comment on

The JavaFan code is the fastest. My code is 2nd. There is no 3rd, 4th or 5th place. Things go "downhill" very fast (not just factor of 2x, 3x, but orders of magnitude).

Actually, so does yours. It's just not visible because of the very limited range. Upping the range to 1..90 gives:

Benchmark: running JavaFan, Marshall for at least 2 CPU seconds...
   JavaFan:  2 wallclock secs ( 2.18 usr +  0.00 sys =  2.18 CPU) @ 44
+81.19/s (n=9769)
  Marshall:  1 wallclock secs ( 2.00 usr +  0.00 sys =  2.00 CPU) @ 34
+2.50/s (n=685)
[download]

Also note that your move to put the assignment of $PHI inside the subroutine reduced the running speed by about 10% (it does 5063.11 iterations/s with $PHI only assigned to once).

Incrementing the range even further would increase the difference even more, but for some N between 90 and 100, F(N) no longer fits inside a 64bit integer. And I didn't want to spend the time to write a benchmark using Math::BigFloat/Math::BigInt.

In reply to Re^2: Explain Fibonacci one-liner ?? by JavaFan
in thread Explain Fibonacci one-liner ?? by Anonymous Monk

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Do you know where your variables are?
	PerlMonks