GNU bug report logs - #75574
Adaptive read buffering is a pessimization

Previous Next

Full log

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

From: Eli Zaretskii <eliz <at> gnu.org>
To: Stefan Kangas <stefankangas <at> gmail.com>
Cc: dancol <at> dancol.org, 75574 <at> debbugs.gnu.org, eggert <at> cs.ucla.edu
Subject: Re: bug#75574: Adaptive read buffering is a pessimization
Date: Tue, 11 Feb 2025 14:21:23 +0200

> From: Stefan Kangas <stefankangas <at> gmail.com>
> Date: Mon, 10 Feb 2025 12:55:58 -0800
> Cc: eggert <at> cs.ucla.edu, 75574 <at> debbugs.gnu.org
> 
> Eli Zaretskii <eliz <at> gnu.org> writes:
> 
> > It wasn't just a good idea, though.  It actually helped fix some use
> > cases.
> 
> There is evidence that setting it to nil solved issues too:
> 
> https://yhetil.org/emacs-bugs/13742752.post <at> talk.nabble.com/
> https://yhetil.org/emacs-bugs/1B2B2EF98D55CB41BD16F13B18B9B0080303EF48 <at> FFBRUE001.cfmu.corp.eurocontrol.int/
> https://yhetil.org/emacs-bugs/873an4b898.fsf__5420.00031932748$1214278000$gmane$org <at> ambire.localdomain/
> 
> > We could begin by setting this variable nil by default and see if
> > someone complains.  If enough time has passed without any complaints,
> > we could then consider actually removing the feature.
> 
> So let's do that.  I have now changed the default on master (commit
> 8437bcb5c96).
> 
> Does anyone object to also marking the variable as obsolete now?

I suggest to first see if the new setting causes any problems.
There's no need to hurry with obsoleting it, since un-obsoleting is a
problematic process, as we've seen in the past.

Previous Next

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