[Teammetrics-discuss] Never ending nntpstat problems
Sukhbir Singh
sukhbir.in at gmail.com
Thu Dec 8 10:07:01 UTC 2011
> It is *definitely* the best approach. I noticed in several cases that
> you tend to keep a lot in memory what in principle is data ready for
I admit that that is correct, but I don't know why I do it. After you
had pointed out, I had stopped following this approach.
> You do not need to care about I/O activity yourself! That's the job of
> your operating system which will cache writing anyway (if you do not
> explicitely call fflush - well, that's C, but there will be a similar
> Python command). So just write any data that can be written once you
> see no need for changing them any more.
That's right, but in this case I thought that it would involve
repeated disk writes for each message and hence I avoided this
approach.
I will fix it.
More information about the Teammetrics-discuss
mailing list