> Here's a bigger question, now that I've read the paper and briefly
> scanned the code. Do you have some thoughts on the long term ability
> of vx32 to get close to unity performance on a system (like Plan 9)
> with a high rate of context switches between file server processes
> (you allude ot this cost in the paper). It's an ideal terminal right
> now. I don't see a need to use drawterm any more.
>
> But running fossil and venti, it's got a ways to go in terms of
> performance (i.e. mk clean in /sys/src/9/pc takes ~60 seconds).
import(1)'ed files, host files and ramfs files are similarly slow.
this is no benchmark, and it's a bit questionable because it's
right on the limit of time's measurement, but it does reflect
a lag i see that i don't see in drawterm:
drawterm (the file is 4368 bytes),
>/dev/null time cat usps.jpg
0.00u 0.00s 0.00r cat usps.jpg
9vx
>/dev/null time cat usps.jpg
0.00u 0.00s 0.01r cat usps.jpg
- erik
