|[hatari-devel] Hatari WinUAE speed comparisons with Falcon030 / 16MHz|
[ Thread Index |
| More lists.tuxfamily.org/hatari-devel Archives
- To: hatari-devel@xxxxxxxxxxxxxxxxxxx
- Subject: [hatari-devel] Hatari WinUAE speed comparisons with Falcon030 / 16MHz
- From: Douglas Little <doug694@xxxxxxxxxxxxxx>
- Date: Fri, 19 Sep 2014 18:28:12 +0100
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=DsP1sW+BsyBFog8LmfnGAVCWHCfXNYH08Olrptp9Kso=; b=UCMQ7demPd7cho/pPIZtTHDYB1lrUl/smxBQyE/DQHC1BQD9c5k39JILsOJbrPHMGs wVoE7IE8TJtJZsmHv9HoWJ1zIV75W5pyrN+nEVsJvGduEZo32OTimD9RNeLmyLuMTKC3 2+Lt/XFTCJvHg03q/3Y66vKRRoCxLDdNtt4QNOw/1fTZY3W5tm/RLonpyPGmp/gutZhH ClKViA1E1neyIbKBEVMOlaaKwHmW4vDmCc5bk6dwvN1l76iB+ibX2RAN/AGtnn1KyujL RNZUIutUNZgpLe5wzmAnzQSjl7waZtqVCK5kkkHfYe1AhedESkFqVCllMvw2idbrDt+d A+2w==
While working on a profiler tool, I captured some performance differences between Hatari and a real Falcon.
The profile captures differences on just two instructions - a trivial ALU instruction (add.l Dn,Dn) and a word move (read) operation. The same tests are repeated with different permutations of I/D caches - and PMMU is used to inhibit caching for some tests via custom page descriptors.
The VIDEL was deliberately shut off to limit bus contention on the F30 while the tests were running, to get memory profile results as close to ideal as possible.
The results are quite varied. It is probably most interesting that the F30 results indicate single operations using fractions of a cycle for *anything* involving memory accesses - while pure cached operations round exactly to 16MHz cycles as expected. This is despite the VIDEL bus fetching being disabled. That one is going to be fun to figure out :)
The profiler tests are still very limited but I'll be adding interesting cases as time goes on, particularly around different addressing modes, overlapping fetches, head/tail cycle cases and so on.