bug#71355: 30.0.50; [PATCH] Improve performance of buffered output in Eshell

[Eli Zaretskii]

> Date: Tue, 4 Jun 2024 20:50:52 -0700
> From: Jim Porter <jporterbugs@gmail.com>
> 
> On 6/4/2024 6:55 PM, Jim Porter wrote:
> > On 6/4/2024 2:52 PM, Stefan Kangas wrote:
> >> Could the docstring be expanded to explain what a user can expect to
> >> happen if they increase or decrease this value?
> > 
> > Sure, that makes sense. Essentially, smaller values will be slower, but 
> > may update faster (subject to the redisplay throttling), whereas larger 
> > values are the opposite.
> 
> I've expanded this docstring and a few others, plus added a simple test 
> to make sure Eshell's built-in "cat" still works.

Is 2K indeed the optimal size?  It is about 25 80-column lines, which
is quite a lot.  "Normal" shells send output to the screen in smaller
chunks.  How about 128 instead? or maybe some small multiple of the
line length, like 1 or 2?