From: johnbent@lanl.gov (John Bent)
Subject: [sup-talk] slowdown for "Saving modified thread" ?
Date: Wed, 28 May 2008 08:33:32 -0600 [thread overview]
Message-ID: <1211984497-sup-8026@tangerine.lanl.gov> (raw)
Even since I moved to next in order to get the attachment searchability
(which is awesome, thanks!), I've seen a major slowdown in the time it
takes to "Saving modified thread." Not a huge slowdown but a couple of
noticable seconds in which the CPU spikes.
next reply other threads:[~2008-05-28 14:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-28 14:33 John Bent [this message]
2008-05-28 19:22 ` John Bent
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=1211984497-sup-8026@tangerine.lanl.gov \
--to=johnbent@lanl.gov \
/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