You are not logged in.
well there is a wide range of possiblities why this happens
from my expirience i would say, if the server is heavy loaded there is a resource which is heavy used and your process isn't able to access it immediately
this could be when the kernel begins to swap out or some other process, e.g. a webserver, is spawning childs like crazy which means the kernel needs to handle more processes or there is much I/O
if the server doesn't have much to do i would say the problem either is a remote server or the architecture of the application itself isn't good (e.g. deadlock)
to really know i would suggest using 'strace -p [PID]'
check the manpage for strace
Yeah there are a few possible reasons. But you want to get rid of that, you could try put the process to a higher priority with "nice" command.
gethostbyintuition() is still a dream of mine
-- quoted from bash
Lack of CPU time isn't the cause, so fiddling with nice won't help (except if it was a
priority inversion problem which is then hidden).
vmstat, strace, top etc. are useful to find out what's going on.
Whenever I see behavior like that on my Mac, it's usually because the d*mn hard drive went to sleep and it takes a few seconds for it to wake back up... during which time any program that is trying to access the disk is blocked.
Solution: disable "Put Hard drive to sleep when possible" in the Energy Setting s dialog.
Perhaps other OS's have a similar "feature", I don't know.