tester print4 is slow on remcons

[Jiri Svoboda]

If you telnet into HelenOS and run 'tester print4' the output is excessively slow. It appears that each character is written out and sent over the network separately. Likely buffering that should be happening either in remcons or libc I/O code does not happen.

[Jiri Svoboda]

Apparently this is because the output is written using TPRINTF which prints to stderr stream which is unbuffered (stdout is line-buffered). Not sure whether/how changing this to a buffering variant is a good idea.

[Vojtech Horky]

I think that adding buffering to stderr would break the purpose of seeing the error output as soon as possible. Thus, the only place to add the buffering would be somewhere in remcons. But I think that remcons should remain as simple as possible to be still usable as a debugging aid (e.g. when the GUI stops responding).

Furthermore, print4 is a very special case because under normal circumstances you do not print characters one by one. In my opinion, we should close this as wontfix.

[Jiri Svoboda]

Also, probably part of the problem is that the text fragments are sent in separate TCP segments. Thus some buffering in the sockets/TCP code might help (either implementing Nagle's algorithm or simply not guarateeing the data to be sent uless it is pushed).

[mtravis]

Here is the ​wiki page for Nagel's algorithm