[Openmcl-devel] slow read-char

[Takehiko Abe]

Gary Byers wrote:

>My first guess would be locking, though I'm becoming an advocate of
>saying "profile, don't guess."
>
>If you're able to do WRITE-STRING "aaaaa...." instead of WRITE-CHAR,
>should find that there's a lot less per-char overhead (including 
>locking overhead.)

Does the locking involves in read-char too? My problem is more to
do with read-char. (though there is a speed difference with
write-char, I don't do write-char in the real code.)

At first I suspect that OpenMCL does not do buffering, but then
I saw buffered-stream-mixin.

It may be my system (OSX 10.3 on an ancient G4). Has anyone
notice the difference of read-char speed compared to another
lisp implementation?

Thank you,
T.