From: "Ludovic Courtès" <ludo@gnu.org>
To: bokr@bokr.com
Cc: Raghav Gururajan <rg@raghavgururajan.name>,
Morgan.J.Smith@outlook.com, 56382@debbugs.gnu.org,
Maxim Cournoyer <maxim.cournoyer@gmail.com>,
20255@debbugs.gnu.org
Subject: bug#20255: [bug#56382] [PATCH] gnu: gajim: Use hicolor-icon-theme to avoid crashing on startup
Date: Tue, 19 Jul 2022 10:29:59 +0200 [thread overview]
Message-ID: <871quhwlmg.fsf@gnu.org> (raw)
In-Reply-To: <20220718133318.GA2771@LionPure> (bokr@bokr.com's message of "Mon, 18 Jul 2022 15:33:18 +0200")
Hi,
bokr@bokr.com skribis:
> I'm sure you were just after a quick indication and know what can affect timing,
> but I'm curious:
>
> What would the above results be if you did the second timing
> first, after a power down and cold start?
>
> I'm guessing the kernel file systems are pretty clever about
> caching stuff, especially if you have lots of ram :)
The ‘drop_caches’ command is meant to drop all caches, as if I were
doing it on a cold start.
Ludo’.
prev parent reply other threads:[~2022-07-19 8:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87sfn6asfz.fsf@gnu.org>
[not found] ` <DM5PR03MB31633E3B8D7FB6CF9CD13BE5C5BE9@DM5PR03MB3163.namprd03.prod.outlook.com>
[not found] ` <ff47ca4d7bfe0148f827dac382ca6211@raghavgururajan.name>
[not found] ` <877d4e8r79.fsf@gnu.org>
[not found] ` <87tu7hsupr.fsf@gmail.com>
[not found] ` <87k08a3h0s.fsf@gnu.org>
2022-07-18 11:21 ` bug#20255: [bug#56382] [PATCH] gnu: gajim: Use hicolor-icon-theme to avoid crashing on startup Maxim Cournoyer
[not found] ` <20220718133318.GA2771@LionPure>
2022-07-19 8:29 ` Ludovic Courtès [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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871quhwlmg.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=20255@debbugs.gnu.org \
--cc=56382@debbugs.gnu.org \
--cc=Morgan.J.Smith@outlook.com \
--cc=bokr@bokr.com \
--cc=maxim.cournoyer@gmail.com \
--cc=rg@raghavgururajan.name \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).