From: "Gerd Möllmann" <gerd.moellmann@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Question about bignum usage
Date: Thu, 20 Jun 2024 10:35:14 +0200 [thread overview]
Message-ID: <m2plscnha5.fsf@pro2.fritz.box> (raw)
In-Reply-To: <86ed8snk0p.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 20 Jun 2024 10:36:06 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Gerd Möllmann <gerd.moellmann@gmail.com>
>> Cc: emacs-devel@gnu.org
>> Date: Thu, 20 Jun 2024 08:34:22 +0200
>>
>> Eli Zaretskii <eliz@gnu.org> writes:
>>
>> > Why not? Time values are known to produce bignums, yes.
>>
>> Ok.
>>
>> > What does list-timers show on that system?
>>
>> 1.0s 5.0s auto-revert-buffers
>> 5.4s - undo-auto--boundary-timer
>> 4m 19.0s 5m persistent-scratch-save
>> * 0.1s t show-paren-function
>> * 0.5s t posframe-hidehandler-daemon-function
>> * 0.5s t #f(compiled-function () #<bytecode -0x181a979fe3c9ba30> [jit-lock--antiblink-grace-timer jit-lock-context-fontify])
>> * 0.5s :repeat blink-cursor-start
>> * 1.0s t which-key--update
>
> This means we check for expired times every 100 msec, so yes, we will
> create a lot of bignums. I see something similar here as well.
Thanks.
It isn't a problem, one just have to know why it happens.
In igc, these bignums accumulate pretty quickly to figures like
PVEC_BIGNUM 97199 3110368
and much higher, where the first number is the number of bignums, and
the second is bytes. The number of fonts is also curious.
PVEC_FONT 90422 10868392
But all seem to be GC'd eventually.
next prev parent reply other threads:[~2024-06-20 8:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-20 5:59 Question about bignum usage Gerd Möllmann
2024-06-20 6:26 ` Eli Zaretskii
2024-06-20 6:34 ` Gerd Möllmann
2024-06-20 7:36 ` Eli Zaretskii
2024-06-20 8:35 ` Gerd Möllmann [this message]
2024-06-20 13:07 ` Gerd Möllmann
2024-06-20 13:43 ` Helmut Eller
2024-06-20 14:17 ` Gerd Möllmann
2024-06-20 18:32 ` Gerd Möllmann
2024-06-20 18:37 ` Gerd Möllmann
2024-06-20 18:58 ` Eli Zaretskii
2024-06-20 19:16 ` Gerd Möllmann
2024-06-20 19:25 ` Eli Zaretskii
2024-06-20 19:42 ` Gerd Möllmann
2024-06-20 9:38 ` Mattias Engdegård
2024-06-20 10:02 ` Eli Zaretskii
2024-07-11 14:10 ` Paul Eggert
2024-07-13 9:43 ` Mattias Engdegård
2024-07-14 4:34 ` Paul Eggert
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=m2plscnha5.fsf@pro2.fritz.box \
--to=gerd.moellmann@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.