Page Menu
Home
c4science
Search
Configure Global Search
Log In
Files
F75673924
timer.html
No One
Temporary
Actions
Download File
Edit File
Delete File
View Transforms
Subscribe
Mute Notifications
Award Token
Subscribers
None
File Metadata
Details
File Info
Storage
Attached
Created
Sat, Aug 3, 15:05
Size
3 KB
Mime Type
text/html
Expires
Mon, Aug 5, 15:05 (2 d)
Engine
blob
Format
Raw Data
Handle
19592532
Attached To
rLAMMPS lammps
timer.html
View Options
<HTML>
<CENTER><A HREF = "http://lammps.sandia.gov">LAMMPS WWW Site</A> - <A HREF = "Manual.html">LAMMPS Documentation</A> - <A HREF = "Section_commands.html#comm">LAMMPS Commands</A>
</CENTER>
<HR>
<H3>timer command
</H3>
<P><B>Syntax:</B>
</P>
<PRE>timer args
</PRE>
<LI><I>args</I> = one or more of <I>off</I> or <I>loop</I> or <I>normal</I> or <I>full</I> or <I>sync</I> or <I>nosync</I>
<PRE> <I>off</I> = do not collect or print any timing information
<I>loop</I> = collect only the total time for the simulation loop
<I>normal</I> = collect timer information broken down by sections (default)
<I>full</I> = like <I>normal</I> but also include CPU and thread utilzation
<I>sync</I> = explicitly synchronize MPI tasks between sections
<I>nosync</I> = do not synchronize MPI tasks between sections (default)
</PRE>
<P><B>Examples:</B>
</P>
<PRE>timer full sync
timer loop
</PRE>
<P><B>Description:</B>
</P>
<P>Select the level of detail LAMMPS performs its CPU timings.
</P>
<P>During a simulation run LAMMPS collects information about how much
time is spent in different sections of the code and thus can provide
valuable information for determining performance and load imbalance
problems. This can be done at different levels of detail and
accuracy. For more information about the timing output, see this
<A HREF = "Section_start.html#start_8">discussion of screen output</A>.
</P>
<P>The <I>off</I> setting will turn all time measurements off. The <I>loop</I>
setting will only measure the total time for a run and not collect any
detailed per section information. With the <I>normal</I> setting, timing
information for portions of the timestep (pairwise calculations,
neighbor list construction, output, etc) are collected as well as
information about load imbalances for those sections across
procsessors. The <I>full</I> setting adds information about CPU
utilization and thread utilization, when multi-threading is enabled.
</P>
<P>With the <I>sync</I> setting, all MPI tasks are synchronized at each timer
call which meaures load imbalance more accuractly, though it can also
slow down the simulation. Using the <I>nosync</I> setting (which is the
default) turns off this synchronization.
</P>
<P>Multiple keywords can be specified. For keywords that are mutually
exclusive, the last one specified takes effect.
</P>
<P>IMPORTANT NOTE: Using the <I>full</I> and <I>sync</I> options provides the most
detailed and accurate timing information, but can also have a negative
performance impact due to the overhead of the many required system
calls. It is thus recommended to use these settings only when testing
tests to identify performance bottlenecks. For calculations with few
atoms or a very large number of processors, even the <I>normal</I> setting
can have a measurable negative performance impact. In those cases you
can just use the <I>loop</I> or <I>off</I> setting.
</P>
<P><B>Restrictions:</B> none
</P>
<P><B>Related commands:</B>
</P>
<P><A HREF = "run.html">run post no</A>, <A HREF = "kspace_modify.html">kspace_modify fftbench</A>
</P>
<P><B>Default:</B>
</P>
<P>timer normal nosync
</P>
</HTML>
Event Timeline
Log In to Comment