Re: macOS metal rendering engine in mac port

[Aaron Jensen]

On Sat, May 22, 2021 at 12:57 PM Alan Third <alan@idiocy.org> wrote:
>
> Well, I'm sure we can make that optimisation on the NS port too. ;)

Hah

> > Full screen frame, with line numbers (11k lines):
> >
> > Mac port: 2.88s
> > emacs27-drawing branch: 4.42s
> > master: 6.75s
> >
> > Full screen frame, no line numbers (11k lines):
> >
> > Mac port 2.24s
> > emacs27-drawing branch: 3.13s
> > master: 5.3s
>
> How can the Mac port only see a change of 0.6s while the NS port sees
> a change of 1.3s, when the only change is turning line numbers on or
> off? Line numbers performance should surely be mostly independent of
> the UI toolkit?

No idea. It seems to be percentage based more than fixed for whatever
reason. I built emacs 27 w/ -g3 -O2

> You know, my benchmarking is all over the place. I literally just did
> two runs at 11s and another two at 8.6s. Nothing changed. And I
> regularly see a code change produce an improvement, then undoing the
> change retaining the improvement. It's like rebuilding the exact same
> code base produces a completely different performance result.
>
> I suspect my Mac rides the CPU frequency continuously or something.

Mine are fairly consistent. I imagine hitting thermal would hurt
though and Intel macs love to do that.

What isn't consistent is typing experience. There are times when it's
just like molasses but I can't necessarily reproduce that with
benchmarks. I wonder if the separate threaded IO from the mac port
helps make things feel more consistent in some way.

It'd be great to try an emacs-28 with the 27+flicker patch rendering.
I'd be curious how that'd feel w/ native comp. Maybe that'd make
enough of a difference for me on this screen.

Thanks,

Aaron