From: Nicola Girardi <ng@0x80.stream>
To: 9front@9front.org
Subject: Re: [9front] Question re: RPI video performance
Date: Sun, 04 Dec 2022 21:11:13 +0100 [thread overview]
Message-ID: <3EF78C709F04EA87420C70F7084BCE86@cirno.home> (raw)
In-Reply-To: <CAAJ3RaN5YvgCje+C1HMmCkcMWTi0RfAfUmC-Ufws1wnLUWbyjw@mail.gmail.com>
Quoth Kristo <kristo.ilmari@gmail.com>:
> Hi,
>
> I happen to own the Pi 2 Model B V1.1 and I definitely can't reproduce
> this "3 chars a second" performance with the latest 9front image. For
> example, the speed of scrolling output in a rio terminal is completely
> reasonable.
>
> 0.00u 0.01s 0.66r cat /lib/words
TL;DR I have similar results for this test.
The "3 chars a second" refers to typing in acme window tags. The "cat
/lib/words" test yields different timings based on the window height;
for a very short window it's very fast, for a fullscreen window it's
very slow.
; grep cat./ /dev/text
0.00u 0.01s 0.59r cat /lib/words
0.00u 0.02s 3.04r cat /lib/words
0.00u 0.00s 5.15r cat /lib/words
Also, using a smaller font yields gives better results (the above is
with a large font, more suitable to my eyes).
; echo $font
/lib/font/bit/vga/vga.font
; grep cat./ /dev/text
0.00u 0.01s 0.62r cat /lib/words
0.00u 0.00s 1.02r cat /lib/words
0.00u 0.00s 1.61r cat /lib/words
Using the vga font, typing on acme window tags is faster than 3 chars
a second, but still seeing the window below flicker all the while.
prev parent reply other threads:[~2022-12-04 20:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-02 14:49 Nicola Girardi
2022-12-02 16:21 ` Sigrid Solveig Haflínudóttir
2022-12-03 9:48 ` Nicola Girardi
2022-12-03 10:02 ` Steve Simon
2022-12-03 11:12 ` Nicola Girardi
2022-12-03 11:53 ` Steve Simon
2022-12-03 16:13 ` Nicola Girardi
2022-12-05 17:00 ` Nicola Girardi
2022-12-03 16:13 ` Eckard Brauer
2022-12-04 18:53 ` Kristo
2022-12-04 20:11 ` Nicola Girardi [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3EF78C709F04EA87420C70F7084BCE86@cirno.home \
--to=ng@0x80.stream \
--cc=9front@9front.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).