Utilizing the multithreading schema, we were awaiting more optimizedIf you're using user-level threads (e.g. pthreads) and doing synchronous
time behavior but could not see it. Obviously, during the "reader" is
doing its job, it is blocked; in this time the scheduler could switch
over to "processor" to allow him to process data. In this case we
would have optimized time-behavior.
I/O then it's likely that the whole process is being blocked by the
kernel until the I/O system call returns. To be honest, on a
uniprocessor system you're not likely to get much help from threading in
the situation you describe, even if you do complicated things to get
asynchronous I/O.