Commit b8ed6180 authored by Jonathan Jenkins's avatar Jonathan Jenkins
Browse files

added short "tips" list based on group discussion with Phil"

parent 3d8dcc1c
......@@ -419,6 +419,53 @@ TOOD: fill this in. Each LP needs to send an event to itself at the
beginning of the simulation (explain why). We usually skew these with
random numbers to help break ties right off the bat (explain why).
\section{Best practices quick reference}
NOTE: these may be integrated with the remaining notes or used as a summary of
\subsection{ROSS simulation development}
\item prefer fine-grained, simple LPs to coarse-grained, complex LPs
\item can simplify both LP state and reverse computation implementation
\item ROSS is very good at event processing, likely small difference in
\item consider separating single-source generation of concurrent events with
"feedback" events or "continue" events to self
\item generating multiple concurrent events makes rollback more difficult
\item use dummy events to work around "event-less" advancement of simulation time
\item add a small amount of time "noise" to events to prevent ties
\item prefer more and smaller events to fewer and larger events
\item simplifies individual event processing
\item ROSS uses bounded event structure size in communication, so
smaller bound $\rightarrow$ less communication overhead
\item prefer placing state in event structure to LP state structure
\item simplifies reverse computation -- less persistent state
\item NOTE: tradeoff with previous point - consider efficiency vs.
\item try to implement event processing with only LP-local information
\item reverse computation with collective knowledge is difficult
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment