public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: "dichen at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug debuginfod/31103] periodically malloc_trim()
Date: Thu, 14 Mar 2024 03:42:34 +0000	[thread overview]
Message-ID: <bug-31103-10460-COl0Frxube@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31103-10460@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=31103

--- Comment #6 from Di Chen <dichen at redhat dot com> ---
Thanks Frank, I have debugged with rusage, but the difference between "during"
and "post" is not that obvious. I believe it's due to my small
.debuginfod.sqlite.

```
(gdb) p during
$2 = {ru_utime = {tv_sec = 0, tv_usec = 21790}, ru_stime = {tv_sec = 0, 
    tv_usec = 29003}, {ru_maxrss = 103836, __ru_maxrss_word = 103836}, {
    ru_ixrss = 0, __ru_ixrss_word = 0}, {ru_idrss = 0, __ru_idrss_word = 0}, {
    ru_isrss = 0, __ru_isrss_word = 0}, {ru_minflt = 967, 
    __ru_minflt_word = 967}, {ru_majflt = 0, __ru_majflt_word = 0}, {
    ru_nswap = 0, __ru_nswap_word = 0}, {ru_inblock = 0, 
    __ru_inblock_word = 0}, {ru_oublock = 128, __ru_oublock_word = 128}, {
    ru_msgsnd = 0, __ru_msgsnd_word = 0}, {ru_msgrcv = 0, 
    __ru_msgrcv_word = 0}, {ru_nsignals = 0, __ru_nsignals_word = 0}, {
    ru_nvcsw = 1229, __ru_nvcsw_word = 1229}, {ru_nivcsw = 1, 
    __ru_nivcsw_word = 1}}
(gdb) p post
$3 = {ru_utime = {tv_sec = 0, tv_usec = 21790}, ru_stime = {tv_sec = 0, 
    tv_usec = 30393}, {ru_maxrss = 103836, __ru_maxrss_word = 103836}, {
    ru_ixrss = 0, __ru_ixrss_word = 0}, {ru_idrss = 0, __ru_idrss_word = 0}, {
    ru_isrss = 0, __ru_isrss_word = 0}, {ru_minflt = 967, 
    __ru_minflt_word = 967}, {ru_majflt = 0, __ru_majflt_word = 0}, {
    ru_nswap = 0, __ru_nswap_word = 0}, {ru_inblock = 0, 
    __ru_inblock_word = 0}, {ru_oublock = 128, __ru_oublock_word = 128}, {
    ru_msgsnd = 0, __ru_msgsnd_word = 0}, {ru_msgrcv = 0, 
    __ru_msgrcv_word = 0}, {ru_nsignals = 0, __ru_nsignals_word = 0}, {
    ru_nvcsw = 1273, __ru_nvcsw_word = 1273}, {ru_nivcsw = 1, 
    __ru_nivcsw_word = 1}}


[Thu 14 Mar 2024 03:22:47 AM GMT] (4738/4749): grooming database
[Thu 14 Mar 2024 03:22:47 AM GMT] (4738/4749): database record counts:
[Thu 14 Mar 2024 03:22:47 AM GMT] (4738/4749): file d/e 0
[Thu 14 Mar 2024 03:22:47 AM GMT] (4738/4749): file s 0
[Thu 14 Mar 2024 03:22:47 AM GMT] (4738/4749): archive d/e 0
[Thu 14 Mar 2024 03:22:47 AM GMT] (4738/4749): archive sref 0
[Thu 14 Mar 2024 03:22:47 AM GMT] (4738/4749): archive sdef 0
[Thu 14 Mar 2024 03:22:47 AM GMT] (4738/4749): buildids 0
[Thu 14 Mar 2024 03:22:47 AM GMT] (4738/4749): filenames 0
[Thu 14 Mar 2024 03:22:47 AM GMT] (4738/4749): fileparts 0
[Thu 14 Mar 2024 03:22:47 AM GMT] (4738/4749): files scanned (#) 0
[Thu 14 Mar 2024 03:22:47 AM GMT] (4738/4749): files scanned (mb) 0
[Thu 14 Mar 2024 03:22:47 AM GMT] (4738/4749): index db size (mb) 21
[Thu 14 Mar 2024 03:22:47 AM GMT] (4738/4749): groomed database in 0.0129799s
```

Do you know where I can get a big .debuginfod.sqlite, so that I can measure the
performance on it?

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2024-03-14  3:42 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-30 20:58 [Bug debuginfod/31103] New: " fche at redhat dot com
2024-01-31 23:19 ` [Bug debuginfod/31103] " dichen at redhat dot com
2024-03-01 11:49 ` dichen at redhat dot com
2024-03-01 13:25 ` fche at redhat dot com
2024-03-02 20:58 ` mark at klomp dot org
2024-03-12 11:43 ` dichen at redhat dot com
2024-03-12 12:39 ` fche at redhat dot com
2024-03-14  3:42 ` dichen at redhat dot com [this message]
2024-03-14 13:22 ` fche at redhat dot com
2024-03-15  1:54 ` dichen at redhat dot com
2024-03-15 12:29 ` fche at redhat dot com
2024-03-18  1:35 ` dichen at redhat dot com
2024-03-19 11:06 ` fche at redhat dot com
2024-03-19 12:14 ` dichen at redhat dot com

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=bug-31103-10460-COl0Frxube@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=elfutils-devel@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).