# Multiple outputs performance **URL:** \ **Category:** Dash Python\ **Created:** [May 15, 2019, 1:43pm UTC](https://community.plotly.com/t/multiple-outputs-performance/23488 "2019-05-15T13:43:48Z")\ **Posts on this page:** 1\ **Showing post:** 4
**Author:** ![Damian](https://avatars.discourse-cdn.com/v4/letter/d/34f0e0/32.png) [@Damian](https://community.plotly.com/u/Damian)\ **Post date:** [May 16, 2019, 1:52pm UTC](https://community.plotly.com/t/multiple-outputs-performance/23488/4 "2019-05-16T13:52:01Z")
> [@OliverBrace](#): > > Is it possible that using the multiple callback could result in a change in the order than callbacks get run? If callbacks are triggering other callbacks then yes you are ultimately generating a different graph of callbacks which will result in a different sequence of how they are called. Have you tried using the new dev tools to investigate? > [@mega Announcing Dash Dev Tools](https://community.plotly.com/t/announcing-dash-dev-tools/22481): > > Dash Dev Tools is our latest effort to provide a pleasant and productive experience for Dash app developers heart Dash DevTools is a built-in debugging UI that provides three main features for Dash developers: A visualization of the callback flow via a DAG visualization (directed acyclic graph) A central place to view both front-end and back-end errors Deep component property validation that bubbles up subtle, inconspicuous bugs bugGetting Started Try it out in the latest version: pip… FYI I have a page that originally had 300 callbacks on it and I reduced it to around 25, the page performance is remarkably better but I did very specifically thinking about how callbacks were triggering each other. --- _[View the full topic](https://community.plotly.com/t/multiple-outputs-performance/23488)._