[hatari-devel] Hatari UI; Installation and Syntax

[Eero Tamminen]

Hi,

On perjantai 31 joulukuu 2010, David Savinkoff wrote:
> I did a quick check with 'top' and a recent hatari using Blue and Flu:
> 
> Falcon with no dsp, no frameskip (and all deluxe options) TOS 4.04 ...
> GEM desktop idles at 79% CPU ... Both Blue and Flu run at 84% CPU.
>
> ST and STE (TOS 206UK) with deluxe options idles the desktop at 20% CPU;
> this is the performance I've always had with Hatari.

With "Patch Timer-D" option enabled in both Falcon & ST?

Compatibility list lists only couple of games with which it has some
effect on rasters & sound speed, otherwise it's fine for everything
and can speed things a lot, especially in ST emulation where interrupt
handling takes relatively larger part of the Hatari CPU consumption.


> I believe these numbers are reasonable and I don't believe there is
> a problem.

One of the reasons why Falcon idle is so high and ST so low is that Falcon
emulation always converts/draws the whole screen whereas ST emulation
does that only for the changed parts.

Same might be useful for Falcon emulation also in modes with less colors
(e.g. 4 or less bits), but it would complicate the code quite a bit and help
only for stuff that updates only small parts of screen.


> 998.418 MHz Pentium3 (1996.83 BogoMIPS) CentOS 5.5 with some
> of my PIII customized, optimized and recompiled packages
> (xorg, SDL, mesa, hatari ...)
> My puddle-jumper does at least warp 1.


	- Eero