On 08/01/2014 09:30, Keith Winston wrote:
well, fair enough. Generally, the issue involves instances when Python
will come back, but it might take several minutes or much longer. And
weird behaviour ensues: like timers I put on the program don't actually
time the amount of time it's busy (by a very, very large margin). Also,
often several minutes after such a thing (sometimes quite a bit later),
things will suddenly start working quickly again. Also, on my laptop I
can actually tell when it's struggling, b/c the fan turns on and/or
speeds up, and in many of these cases it will go into all-out mode,
even though I'm not doing anything. But your point about having no lever
with which to move the world is a good one.
Typical symptoms of hammering a system particularly when you start
swapping memory to and from disk. The usual solution is to find a
better algorithm or buy more ram :)
A slight aside you've managed to lose all of my context, more problems
with gmail I take it?
--
My fellow Pythonistas, ask not what our language can do for you, ask
what you can do for our language.
Mark Lawrence
_______________________________________________
Tutor maillist - Tutor@python.org
To unsubscribe or change subscription options:
https://mail.python.org/mailman/listinfo/tutor
