The
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, for example ets tables, processes or ports. In other cases it protects a
specific range of a resource, for example
Some locks in the system are static and protects global resources, for example
Starts the lock profiler server. The server only act as a medium for the
user and performs filtering and printing of data collected by
Stops the lock profiler server.
Same as
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.
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.
Same as
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.
Same as
Prints a list of internal locks and its statistics.
For option description, see
Same as
Prints a list of internal lock counters by source code locations.
For option description, see
Same as
Prints a list of internal lock counters for a specific lock.
Lock
Option description:
Prints lcnt server state and generic information about collected lock statistics.
Swaps places on
Restores previously saved data to the server.
Saves the collected data to file.
The following functions are used for convenience.
Same as
Clears the lock counters and then setups the instrumentation to save all destroyed locks.
After setup the fun is called, passing the elements in
Clears the lock counters and then setups the instrumentation to save all destroyed locks.
After setup the function is called, passing the elements in
Same as
Creates a process id with creation 0. Example:
Same as
Creates a port id with creation 0.
The following functions control the behavior of the internal counters.
Same as
Returns a list of raw lock counter data.
Same as
Clear the internal counters. Same as
Same as
Changes the lock counter behavior and returns the previous behaviour.
Option description: