Skip to content

Performance considerations#

Wake testing framework is designed to be fast and efficient. However, there are some things to keep in mind to achieve the best performance.

  1. Always prefer to use Anvil whenever possible.
  2. Always prefer WebSockets connection over HTTP connection.
  3. Avoid accessing transaction events ( unless necessary. Consider using tx.raw_events instead.
  4. Avoid using accounts other than the pre-generated ones (chain.accounts) in from_ parameters. If you need more accounts than the default number, change the Wake configuration file or launch the development chain with a higher number of accounts and connect to it.
  5. Minimize usage of call traces (tx.call_trace) and console logs (tx.console_logs). These features are useful for debugging, but may slow down the test execution.

Profiling tests#

Every Wake command has the --profile flag that can be used to profile the test execution. The profiling results are saved in the .wake/ file.

wake --profile test tests/


It is important to specify the --profile flag before the test command.

It is not recommended to profile the wake test command in multiprocessing mode (with the -P option set).

Wake uses cProfile dump_stats method to save the profiling results.


gprof2dot is a great tool for visualizing the profiling results. Together with Graphviz, it can be used to generate a call graph of the test execution.

gprof2dot -f pstats .wake/ | dot -Tsvg -o