Related:

• eal time 1. [techspeak] adj. Describes an application which requires a program to respond to stimuli within some small upper limit of response time (typically milli- or microseconds).
  Process control at a chemical plant is the canonical example....
• deadlock: n. 1. [techspeak] A situation wherein two or more processes are unable to proceed because each is waiting for one of the others to do something.
  A common example is a program communicating to a server, which may find itself waiting for output from the server before sending anything more to it, while the server is similarly waiting for more input from the controlling program before outputting anything....
• cycle: 1. n. The basic unit of computation. What every hacker wants more of (noted hacker Bill Gosper describes himself as a "cycle junkie").
  One can describe an instruction as taking so many `clock cycles'....
• hell [orig. Multics n. techspeak, widely propagated via Unix] 1.
  [techspeak] The command interpreter used to pass commands to an operating system...
• bum: 1. vt. To make highly efficient, either in time or space, often at the expense of clarity.
  I managed to bum three more instructions out of that code....
• deadlock n. 1. [techspeak] A situation wherein two or more processes are unable to proceed because each is waiting for one of the others to do something.
  A common example is a program communicating to a server, which may find itself waiting for output from the server before sending anything more to it, while the server is similarly waiting for more input from the controlling program before outputting anything....
• control-C: vi. 1. "Stop whatever you are doing." From the interrupt character used on many operating systems to abort a running program.
  Considered silly. 2. interj. Among BSD UNIX hackers, the canonical humorous response to "Give me a break!...
• wall time: n. (also `wall clock time') 1. `Real world' time (what the clock on the wall shows), as opposed to the system clock's idea of time.
  2. The real running time of a program, as opposed to the number of {tick}s required to execute it (on a timesharing system these always differ, as no one program gets all the ticks, and on multiprocessor systems with good thread support one may get more processor time than real time)....
• glitch: /glich/ [from German `glitschen' to slip, via Yiddish `glitshen', to slide or skid] 1.
  . A sudden interruption in electric service, sanity, continuity, or program function....