19962009Ericsson AB. All Rights Reserved.
The contents of this file are subject to the Erlang Public License,
Version 1.1, (the "License"); you may not use this file except in
compliance with the License. You should have received a copy of the
Erlang Public License along with this software. If not, it can be
retrieved online at http://www.erlang.org/.
Software distributed under the License is distributed on an "AS IS"
basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. See
the License for the specific language governing rights and limitations
under the License.
timerSebastian StrolloBjarne Däcker1Bjarne Däcker1998-09-09Dtimer.sgmltimerTimer Functions
This module provides useful functions related to time. Unless otherwise
stated, time is always measured in milliseconds. All
timer functions return immediately, regardless of work carried
out by another process.
Successful evaluations of the timer functions yield return values
containing a timer reference, denoted TRef below. By using
cancel/1, the returned reference can be used to cancel any
requested action. A TRef is an Erlang term, the contents
of which must not be altered.
The timeouts are not exact, but should be at least as long
as requested.
start() -> okStart a global timer server (named timer_server).
Starts the timer server. Normally, the server does not need
to be started explicitly. It is started dynamically if it
is needed. This is useful during development, but in a
target system the server should be started explicitly. Use
configuration parameters for kernel for this.
apply_after(Time, Module, Function, Arguments) -> {ok, Tref} | {error, Reason}Apply Module:Function(Arguments)after a specified Time.Time = integer() in MillisecondsModule = Function = atom()Arguments = [term()]
Evaluates apply(M, F, A) after Time amount of time
has elapsed. Returns {ok, TRef}, or {error, Reason}.
Evaluates Pid ! Message repeatedly after Time
amount of time has elapsed. (Pid can also be an atom of
a registered name.) Returns {ok, TRef} or
{error, Reason}.
send_interval/2
Same as send_interval(Time, self(), Message).
cancel(TRef) -> {ok, cancel} | {error, Reason}Cancel a previously requested timeout identified by TRef.
Cancels a previously requested timeout. TRef is a unique
timer reference returned by the timer function in question. Returns
{ok, cancel}, or {error, Reason} when TRef
is not a timer reference.
sleep(Time) -> okSuspend the calling process for Timeamount of milliseconds.Time = integer() in milliseconds or the atom infinity
Suspends the process calling this function for Time amount
of milliseconds and then returns ok, or suspend the process
forever if Time is the atom infinity. Naturally, this
function does not return immediately.
tc(Module, Function, Arguments) -> {Time, Value}Measure the real time it takes to evaluate apply(Module, Function, Arguments)Module = Function = atom()Arguments = [term()]Time = integer() in microsecondsValue = term()
Evaluates apply(Module, Function, Arguments) and measures
the elapsed real time as reported by now/0.
Returns {Time, Value}, where
Time is the elapsed real time in microseconds,
and Value is what is returned from the apply.
Returns the number of milliseconds in Hours + Minutes + Seconds.
Examples
This example illustrates how to print out "Hello World!" in 5 seconds:
1> timer:apply_after(5000, io, format, ["~nHello World!~n", []]).
{ok,TRef}
Hello World!
The following coding example illustrates a process which performs a
certain action and if this action is not completed within a certain
limit, then the process is killed.
Pid = spawn(mod, fun, [foo, bar]),
%% If pid is not finished in 10 seconds, kill him
{ok, R} = timer:kill_after(timer:seconds(10), Pid),
...
%% We change our mind...
timer:cancel(R),
...WARNING
A timer can always be removed by calling cancel/1.
An interval timer, i.e. a timer created by evaluating any of the
functions apply_interval/4, send_interval/3, and
send_interval/2, is linked to the process towards which
the timer performs its task.
A one-shot timer, i.e. a timer created by evaluating any of the
functions apply_after/4, send_after/3,
send_after/2, exit_after/3, exit_after/2,
kill_after/2, and kill_after/1 is not linked to any
process. Hence, such a timer is removed only when it reaches its
timeout, or if it is explicitly removed by a call to cancel/1.