From: "Frank Ch. Eigler" <fche@redhat.com>
To: "Josef Čejka" <jcejka@suse.de>
Cc: "elfutils-devel@sourceware.org" <elfutils-devel@sourceware.org>
Subject: Re: [PATCH 1/1] debuginfod: create indexes to speed up grooming
Date: Sat, 30 Jul 2022 09:07:13 -0400 [thread overview]
Message-ID: <20220730130713.GA23943@redhat.com> (raw)
In-Reply-To: <3605019.RUnXabflUD@dhcp107>
Hi -
> Create indexes on _r_de and _f_de tables
> to speed up delete operations called by groom() function.
> Primary keys of those tables are optimalized to search rows
> by buildids so delete by file and mtime attributes
> has to scan the whole table. [...]
By the way, another possible approach to this is could be to create
those indexes only for the duration of a groom operation: Create at
start, drop at end. It'd speed up a set of delete's almost as well,
and also save disk space during normal operations. OTOH, the peak
disk space requirement would be the same, so if the server's running
low on index storage disk, it'll fail either way, so probably not
worth doing this.
- FChE
prev parent reply other threads:[~2022-07-30 13:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-29 15:49 Josef Čejka
2022-07-29 16:15 ` Frank Ch. Eigler
2022-07-30 13:07 ` Frank Ch. Eigler [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=20220730130713.GA23943@redhat.com \
--to=fche@redhat.com \
--cc=elfutils-devel@sourceware.org \
--cc=jcejka@suse.de \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).