GNU bug report logs - #16800
24.3; flyspell works slow on very short words at the end of big file

Previous Next

Full log

Message #89 received at 16800 <at> debbugs.gnu.org (full text, mbox):

From: Agustin Martin <agustimartin <at> gmail.com>
To: Aleksey Cherepanov <aleksey.4erepanov <at> gmail.com>, 16800 <at> debbugs.gnu.org
Subject: Re: bug#16800: 24.3; flyspell works slow on very short words at the
 end of big file
Date: Sun, 9 Mar 2014 18:36:55 +0100

[Message part 1 (text/plain, inline)]

2014-03-02 4:56 GMT+01:00 Eli Zaretskii <eliz <at> gnu.org>:

> > Date: Sun, 2 Mar 2014 01:44:27 +0400
> > From: Aleksey Cherepanov <aleksey.4erepanov <at> gmail.com>
> > Cc: Agustin Martin <agustin.martin <at> hispalinux.es>, 16800 <at> debbugs.gnu.org
> >
> > We could try to limit execution time. Though checks for that could
> > slow down the search.
>
> Exactly.
>

I see other problem with that, it is not deterministic, since the limit
depends on system load.

I have mixed feelings about changing current default from unlimited, but I
slowly changing my mind towards having  a big but not unlimited value as
default.

On the one hand, not putting limits in default value looks nicer, but on
the other that may have a non negligible impact in performance for really
huge files, as Eli points out.

Alexey's one-liner is 30000 lines and 2.4e6 chars size. While new code
seems to work for it, I'd put the limit somewhere lower, no more than 1e6.
This should be huge enough for any practical use and for anyone to notice
the difference.

Regards,

-- 
Agustin

[Message part 2 (text/html, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.