WP-34S function execution speed ? - Printable Version +- HP Forums (https://archived.hpcalc.org/museumforum) +-- Forum: HP Museum Forums (https://archived.hpcalc.org/museumforum/forum-1.html) +--- Forum: Old HP Forum Archives (https://archived.hpcalc.org/museumforum/forum-2.html) +--- Thread: WP-34S function execution speed ? (/thread-249433.html) |
WP-34S function execution speed ? - Gene Wright - 09-03-2013 Is there a table somewhere that lists the functions and how long it takes for each to execute? I know some are variable depending on the input arguments, but I didn't see such a table in the manual. For example, something like this: + 5ms - 11ms SIN 200ms etc
Re: WP-34S function execution speed ? - Paul Dale - 09-04-2013 No. Fast or slow mode? With or without crystal? Which firmware version?
Re: WP-34S function execution speed ? - Gene Wright - 09-04-2013 Pauli, that's an answer I would expect from HP! :-) I think several versions should be available. At the very least, non-crystal, slow mode, version 2 and version 3 firmware. I would suspect a very small percentage of units have the crystal. Fast mode could be generalized as X% faster than slow mode.
It seems to me :-) that *some* list should be available...or else how will non-developers know which instructions slow down their programming contest entries this year at HHC 2013?
Re: WP-34S function execution speed ? - Steve Simpkin - 09-04-2013 Quote: Some mysteries are better left discovered. The fun is in the journey, the destination is the reward. Re: WP-34S function execution speed ? - Paul Dale - 09-04-2013 Quote: Non crystal timings are quite variable. That is the point of having a crystal. Firmware versions would ideally have to be more finely grained than just 2 and 3. Marcus and I made a lot of space/time tradeoffs during the development of 3. The obvious way to deal with this is to benchmark the latest version 2 and version 3 revisions. Firmware version 3 is unlikely to change significantly now so it wouldn't need regular major revisions anymore.
Quote: Sounds like you've found a project :-) It is straightforward to write timing loops using the TICKS command and check each instruction as required. That's what I've done in the past when performance was an issue (re-implementing LN mostly). Something along the lines of:
LBL A I don't believe anyone knows the instruction timings -- I certainly don't. For most instructions I don't even have a feel as to their relative timings. One thing I am confident about, however, is that Version 2 firmware will be faster than version 3 pretty much across the board. Many space for time tradeoffs were made in version 3 to squeeze the significant extra functionality in.
|