From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] Beginner questions
Date: Mon, 19 May 2008 16:38:40 -0700 [thread overview]
Message-ID: <1211240148-sup-2640@south> (raw)
In-Reply-To: <481F521A.8030207@gmail.com>
Reformatted excerpts from yanghatespam's message of 2008-05-05:
> Does anybody else find sup to be very slow at displaying these
> threads? I can literally see the threads trickling into view.
It's slower than it could be. I would like to cache the threading
(possibly directly in the index), as it's recomputed each time and even
though Ferret is fast, it could be faster.
> sup feels sluggish overall (even moving the arrows around in
> inbox-mode has a slight delay, such that I can only move by about 30
> lines per second).
Another thing I would love to fix. Profiling is the first step.
--
William <wmorgan-sup at masanjin.net>
next prev parent reply other threads:[~2008-05-19 23:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-05 0:47 Yang Zhang
2008-05-05 1:02 ` Daniel Wagner
2008-05-05 2:08 ` Yang Zhang
2008-05-05 18:09 ` Marc Hartstein
2008-05-05 18:29 ` Yang Zhang
2008-05-19 23:38 ` William Morgan [this message]
2008-05-06 2:15 ` Christopher Warrington
2008-05-05 2:48 kendall at clarkparsia.com
2008-05-19 23:44 ` William Morgan
2008-08-03 23:17 Thorsten Kramer
2008-08-04 1:41 ` William Morgan
2008-08-05 21:52 ` Thorsten Kramer
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=1211240148-sup-2640@south \
--to=wmorgan-sup@masanjin.net \
/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