Skip to content
GitLab
Menu
Projects
Groups
Snippets
Loading...
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
Menu
Open sidebar
Xin Wang
codes-dev
Commits
b8ed6180
Commit
b8ed6180
authored
Dec 09, 2013
by
Jonathan Jenkins
Browse files
added short "tips" list based on group discussion with Phil"
parent
3d8dcc1c
Changes
1
Hide whitespace changes
Inline
Side-by-side
doc/codes-best-practices.tex
View file @
b8ed6180
...
...
@@ -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
section(s).
\subsection
{
ROSS simulation development
}
\begin{enumerate}
\item
prefer fine-grained, simple LPs to coarse-grained, complex LPs
\begin{enumerate}
\item
can simplify both LP state and reverse computation implementation
\item
ROSS is very good at event processing, likely small difference in
performance
\end{enumerate}
\item
consider separating single-source generation of concurrent events with
"feedback" events or "continue" events to self
\begin{enumerate}
\item
generating multiple concurrent events makes rollback more difficult
\end{enumerate}
\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
\begin{enumerate}
\item
simplifies individual event processing
\item
ROSS uses bounded event structure size in communication, so
smaller bound
$
\rightarrow
$
less communication overhead
\end{enumerate}
\item
prefer placing state in event structure to LP state structure
\begin{enumerate}
\item
simplifies reverse computation -- less persistent state
\item
NOTE: tradeoff with previous point - consider efficiency vs.
complexity
\end{enumerate}
\item
try to implement event processing with only LP-local information
\begin{enumerate}
\item
reverse computation with collective knowledge is difficult
\end{enumerate}
\end{enumerate}
\section
{
TODO
}
\begin{itemize}
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment