Performance Do’s and Don’ts

FleCSI’s programming model enables asynchronous parallel performance. This is a partial list of patterns (do’s) and anti-patterns (don’ts) that have significant performance consequences.

---

Do Activate Tracing Around Your flecsi::execute<> Loops

• Performance Effect of Tracing
• Implementing Tracing in Your Code
• Enabling Trace Replay on the Command Line
• When to Use Tracing

Don’t Block the Top-Level Task (TLT)

• Performance Effect of get() Outside of a Task
• Forcing Bulk-Synchronousity in Your Code
• Removing Bulk-Synchronousity from Your Code
• When to Call get() Outside of a Task