hmm. None of those figures seem to be maxxing out the core resources...
Bottleneck elsewhere perhaps...
McGivering a similar test together now. (I hope)
EDIT: OKAY... I followed these instructions:
https://www.mobileread.com/forums/sho...&postcount=326
and I can confirm that there is about a 1 to 2 seconds delay at the very most....
perhaps less.
This is using Linux & DX.
even scrolling around like crazy (which to be honest has very little value in term of usefulness) I didn't manage more than 69% cpu consumption.
The average was around 15%
Mem sat at about a 20% footprint, which again is nominal.
To be honest it was pretty decent as experiences go.
Not sure I would be super happy using it as a screen full time, and true, my typing sucks...
But yeah. not too bad. Certainly not way behind.
The vnc only occasionally did the odd "dumb" update or two:
Quote:
partially updating eink display (0,0)-(784,571)
partially updating eink display (0,0)-(479,1020)
partially updating eink display (0,0)-(822,1021)
partially updating eink display (823,100)-(0,1020)
partially updating eink display (823,100)-(0,1020)
partially updating eink display (0,0)-(822,1021)
partially updating eink display (448,100)-(635,950)
partially updating eink display (448,100)-(511,1020)
partially updating eink display (480,122)-(822,950)
partially updating eink display (823,100)-(0,950)
|
and mainly handled the partial updating pretty decently.
sorry I can't find the bottleneck. Frankly I don't see one.
I did get the very occasional
error while handling RFB message.
but meh.
apologies about that.
and yeah.... I also don't know how to scrape htop so we can be embarrassed together.