Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.sys.apple2.programmer > #2820

Re: Benchmark / Profiling / Timing on real hardware (Apple //e, //c,Laser 128) ?

Show all headers | View raw

Michael Pohoreski wrote:
> Let's say I want to benchmark my asm. code that slurps ##K off a custom
> RWTS.
> 
> How would I go about benchmarking / profiling / timing this on real
> hardware? 
> Primary will be an enhanced Apple //e, along with optional Apple //c, and
> a
> Laser 128.
> 
> I don't mean at the granularity of clock cycle timing (I already have
> AppleWin's TRACE for that :-) and the 602 tables), but of the granularity
> of Seconds and Milliseconds.
> 
> Minimum second accuracy is required (maximum would be ~2 minutes). 
> Millisecond timing would just be a sweet bonus.
> 
> NOTES:
> 
>  * I just picked up another ThunderClock Plus so that is what I'm thinking
>  will be the primary means of a clock source.
> 
>  * I also have the "No-Slot" option coming soon too ...
> https://www.ultimateapple2.com/catalogzen154/index.php?main_page=product_info&products_id=70
> 
> I have not searched usenet / forums -- I'll do that later. :-)
> 
> TIA !
> Michael
>fetaure
May I suggest that you get a look at the timing measurement routines I wrote
for the companion program of a utility I've written in the past months.
I've used them to evaluate the performance gain I get by using some features
of the utility instead of using plain vanilla Applesoft code.
The subroutines themselves are written for:
a) The Thunderclock peripheral cards (the first one advertised as being
fully ProDOS compatible) (file TCPRECON.S from source disks);
b) The internal 2GS circuitry (file TCPRECON.S from source disks);
c) The SMT NoSlotClock chip (file SMTRECON.S from source disks)
However, the accuracy I've got would not be above a second of time. That
would mean that many iterations would be measured between two "clock"
circuit pollings to be meaningful.

HopeTHisHelpsAsTheySay,
Benoît



-- 
Growing old is mandatory..
growing up is optional..
But the other way round is as true.

Back to comp.sys.apple2.programmer | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Benchmark / Profiling / Timing on real hardware (Apple //e, //c, Laser 128) ? Michael Pohoreski <michael.pohoreski@gmail.com> - 2016-06-29 12:06 -0700
  Re: Benchmark / Profiling / Timing on real hardware (Apple //e, //c, Laser 128) ? Michael J. Mahon <mjmahon@aol.com> - 2016-06-29 14:17 -0500
  Re: Benchmark / Profiling / Timing on real hardware (Apple //e, //c, Laser 128) ? "Mark D. Overholser" <marko@markoverholser.com> - 2016-06-29 16:11 -0700
    Re: Benchmark / Profiling / Timing on real hardware (Apple //e, //c, Laser 128) ? Michael Pohoreski <michael.pohoreski@gmail.com> - 2016-06-29 17:17 -0700
      Re: Benchmark / Profiling / Timing on real hardware (Apple //e, //c, Laser 128) ? Michael J. Mahon <mjmahon@aol.com> - 2016-06-30 13:51 -0500
        Re: Benchmark / Profiling / Timing on real hardware (Apple //e, //c, Laser 128) ? Michael Pohoreski <michael.pohoreski@gmail.com> - 2016-06-30 11:56 -0700
          Re: Benchmark / Profiling / Timing on real hardware (Apple //e, //c, Laser 128) ? "Mark D. Overholser" <marko@markoverholser.com> - 2016-07-01 09:06 -0700
          Re: Benchmark / Profiling / Timing on real hardware (Apple //e, //c, Laser 128) ? Michael J. Mahon <mjmahon@aol.com> - 2016-07-01 12:15 -0500
            Re: Benchmark / Profiling / Timing on real hardware (Apple //e, //c, Laser 128) ? Michael Pohoreski <michael.pohoreski@gmail.com> - 2016-07-01 12:34 -0700
              Re: Benchmark / Profiling / Timing on real hardware (Apple //e, //c, Laser 128) ? Antoine Vignau <antoine.vignau@laposte.net> - 2016-07-01 14:59 -0700
                Re: Benchmark / Profiling / Timing on real hardware (Apple //e, //c, Laser 128) ? Michael J. Mahon <mjmahon@aol.com> - 2016-07-02 03:03 -0500
                Re: Benchmark / Profiling / Timing on real hardware (Apple //e, //c, Laser 128) ? Michael Pohoreski <michael.pohoreski@gmail.com> - 2016-07-02 10:21 -0700
                Re: Benchmark / Profiling / Timing on real hardware (Apple //e, //c, Laser 128) ? David Schmenk <dschmenk@gmail.com> - 2016-07-02 13:40 -0700
          Re: Benchmark / Profiling / Timing on real hardware (Apple //e, //c, Laser 128) ? "Mark D. Overholser" <marko@markoverholser.com> - 2016-07-02 20:45 -0700
  Re: Benchmark / Profiling / Timing on real hardware (Apple //e, //c, Laser 128) ? John Brooks <jbrooks@blueshiftinc.com> - 2016-07-01 22:52 -0700
  Re: Benchmark / Profiling / Timing on real hardware (Apple //e, //c,Laser 128) ? Benoit0123 <bgilon@free.fr> - 2016-07-04 11:54 +0000
    Re: Benchmark / Profiling / Timing on real hardware (Apple //e, //c,Laser 128) ? Michael J. Mahon <mjmahon@aol.com> - 2016-07-04 18:48 -0500

csiph-web