Subj : exec/load/syncterm_cache.js
To   : Git commit to main/sbbs/master
From : Deuc¨
Date : Sat Dec 28 2024 11:22:06

https://gitlab.synchro.net/main/sbbs/-/commit/2760bfe13b708c4f344de7fb
Modified Files:
	exec/load/syncterm_cache.js
Log Message:
Fix syncterm_cache.js

It was badly broken, especially with large files... we now don't
try console.write() unless there's enough space in
console.output_buffer_space.

On my system (debug build of Synchronet), the most I can push through
console.write() over telnet is about 1.9MB/s.  My release build of
SyncTERM can consume about 4MB/s of string data, so Synchronet is the
choke point in my setup here. (SSH is much worse)

My super-cool demo thing ends up needing about 90 seconds to preload
all the cache stuff, so it's simply not useable, even locally. :(

If I use client.socket.send(), I can unlock the Synchronet throughput,
but I can't remember if client.socket is the passthru socket with SSH
or not... and there's no way to synchronize the socket with the console
at the end of the send (console has flush(), Socket doesn't, and even if
it did, it wouldn't flush through to the output buffer).

---
 þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

.