lcnt
A runtime system Lock Profiling tool.
The lcnt
module is used to profile the internal ethread locks in the
Erlang Runtime System. With lcnt
enabled, Internal counters in the
runtime system are updated each time a lock is taken. The counters stores
information about the number of acquisition tries and the number of collisions
that has occurred during the acquisition tries. The counters also record the
waiting time a lock has caused for a blocked thread when a collision has occurred.
The data produced by the lock counters will give an estimate on how well the runtime system will behave from a parallelizable view point for the scenarios tested. This tool was mainly developed to help erlang runtime developers iron out potential and generic bottlenecks.
Locks in the emulator are named after what type of resource they protect and where
in the emulator they are initialized, those are lock 'classes'. Most of those
locks are also instantiated several times, and given unique identifiers, to increase
locking granularity. Typically an instantiated lock protects a disjunct set of
the resource, i.e ets-tables, processes or ports. In other cases it protects a
specific range of a resource, e.g. pix_lock
which protects index to process
mappings, and is given a unique number within the class. A unique lock in lcnt
is referenced by a name (class) and an identifier, {Name, Id}
.
Some locks in the system are static and protects global resources, for example
bif_timers
and the run_queue
locks. Other locks are dynamic and not
necessarily long lived, for example process locks and ets-table locks. The
statistics data from short lived locks can be stored separately when the locks
are deleted. This behavior is by default turned off to save memory but can be
turned on via lcnt:rt_opt({copy_save, true})
. The lcnt:apply/1,2,3
functions enables this behavior during profiling.
Functions
start() -> {ok, Pid} | {error, {already_started, Pid}}
Pid = pid()
Starts the lock profiler server. The server only act as a medium for the
user and performs filtering and printing of data collected by lcnt:collect/1
.
stop() -> ok
Stops the lock profiler server.
collect() -> ok
Same as collect(node())
.
collect(Node) -> ok
Node = node()
Collects lock statistics from the runtime system. The function starts a server if it is not already started. It then populates the server with lock statistics. If the server held any lock statistics data before the collect then that data is lost.
Note!
When collection occurs the runtime system transitions to a single thread, blocking all other threads. No other tasks will be scheduled during this operation. Depending on the size of the data this might take a long time (several seconds) and cause timeouts in the system.
clear() -> ok
Same as clear(node())
.
clear(Node) -> ok
Node = node()
Clears the internal lock statistics from the runtime system. This does not clear the data on the server only on runtime system. All counters for static locks are zeroed, all dynamic locks currently alive are zeroed and all saved locks now destroyed are removed. It also resets the duration timer.
conflicts() -> ok
Same as conflicts([])
.
conflicts([Option]) -> ok
Option = {sort, Sort} | {reverse, bool()} | {thresholds, [Thresholds]} | {print, [Print | {Print, integer()}]} | {max_locks, MaxLocks} | {combine, bool()}
Sort = name | id | type | tries | colls | ratio | time | entry
Thresholds = {tries, integer()} | {colls, integer()} | {time, integer()}
Print = name | id | type | entry | tries | colls | ratio | time | duration
MaxLocks = integer() | none
Prints a list of internal locks and its statistics.
For option description, see lcnt:inspect/2.
locations() -> ok
Same as locations([])
.
locations([Option]) -> ok
Option = {sort, Sort} | {thresholds, [Thresholds]} | {print, [Print | {Print, integer()}]} | {max_locks, MaxLocks} | {combine, bool()}
Sort = name | id | type | tries | colls | ratio | time | entry
Thresholds = {tries, integer()} | {colls, integer()} | {time, integer()}
Print = name | id | type | entry | tries | colls | ratio | time | duration
MaxLocks = integer() | none
Prints a list of internal lock counters by source code locations.
For option description, see lcnt:inspect/2.
inspect(Lock) -> ok
Same as inspect(Lock, [])
.
inspect(Lock, [Option]) -> ok
Lock = Name | {Name, Id | [Id]}
Name = atom() | pid() | port()
Id = atom() | integer() | pid() | port()
Option = {sort, Sort} | {thresholds, [Thresholds]} | {print, [Print | {Print, integer()}]} | {max_locks, MaxLocks} | {combine, bool()} | {locations, bool()}
Sort = name | id | type | tries | colls | ratio | time
Thresholds = {tries, integer()} | {colls, integer()} | {time, integer()}
Print = name | id | type | entry | tries | colls | ratio | time | duration
MaxLocks = integer() | none
Prints a list of internal lock counters for a specific lock.
Lock Name
and Id
for ports and processes are interchangeable with the use of lcnt:swap_pid_keys/0
and is the reason why pid()
and port()
options can be used in both Name
and Id
space. Both pids and ports are special identifiers with stripped creation and can be recreated with lcnt:pid/2,3 and lcnt:port/1,2.
Option description:
{combine, bool()}
Default:
true
{locations, bool()}
Default:
false
{max_locks, MaxLocks}
none
.
Default:
20
{print, PrintOptions}
name
id
type
rw_mutex
, mutex
, spinlock
, rw_spinlock
or proclock
.entry
{locations, true}
this option prints the lock operations source file and line number entry-points along with statistics for each entry. tries
colls
ratio
time
duration
Default:
[name,id,tries,colls,ratio,time,duration]
{reverse, bool()}
Default:
false
{sort, Sort}
Default:
time
{thresholds, Thresholds}
Default:
[{tries, 0}, {colls, 0}, {time, 0}]
information() -> ok
Prints lcnt server state and generic information about collected lock statistics.
swap_pid_keys() -> ok
Swaps places on Name
and Id
space for ports and processes.
load(Filename) -> ok
Filename = filename()
Restores previously saved data to the server.
save(Filename) -> ok
Filename = filename()
Saves the collected data to file.
Convenience functions
The following functions are used for convenience.
Functions
apply(Fun) -> term()
Same as apply(Fun, [])
.
apply(Fun, Args) -> term()
Fun = fun()
Args = [term()]
Clears the lock counters and then setups the instrumentation to save all destroyed locks.
After setup the fun is called, passing the elements in Args
as arguments.
When the fun returns the statistics are immediately collected to the server. After the
collection the instrumentation is returned to its previous behavior.
The result of the applied fun is returned.
apply(Module, Function, Args) -> term()
Module = atom()
Function = atom()
Args = [term()]
Clears the lock counters and then setups the instrumentation to save all destroyed locks.
After setup the function is called, passing the elements in Args
as arguments.
When the function returns the statistics are immediately collected to the server. After the
collection the instrumentation is returned to its previous behavior.
The result of the applied function is returned.
pid(Id, Serial) -> pid()
Same as pid(node(), Id, Serial)
.
pid(Node, Id, Serial) -> pid()
Node = node()
Id = integer()
Serial = integer()
Creates a process id with creation 0. Example:
port(Id) -> port()
Same as port(node(), Id)
.
port(Node, Id) -> port()
Node = node()
Id = integer()
Creates a port id with creation 0.
Internal runtime lock counter controllers
The following functions control the behavior of the internal counters.
Functions
rt_collect() -> [lock_counter_data()]
Same as rt_collect(node())
.
rt_collect(Node) -> [lock_counter_data()]
Node = node()
Returns a list of raw lock counter data.
rt_clear() -> ok
Same as rt_clear(node())
.
rt_clear(Node) -> ok
Node = node()
Clear the internal counters. Same as lcnt:clear(Node)
.
rt_opt({Type, bool()}) -> bool()
Same as rt_opt(node(), {Type, Opt})
.
rt_opt(Node, {Type, bool()}) -> bool()
Node = node()
Type = copy_save | process_locks
Changes the lock counter behavior and returns the previous behaviour.
Option description:
{copy_save, bool()}
Default:
false
{process_locks, bool()}
Default:
true