Improving speed of dallinger debug: 2pts
See original GitHub issueCurrently the dallinger debug
command runs pretty slowly, often taking 10-15s to launch a local instance of the experiment. This slows down the interactive development cycle. Any ideas about how we might speed up this process? Perhaps have a command-line option that bypasses local Heroku?
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (1 by maintainers)
Top Results From Across the Web
Improve debugging speed - Studio - UiPath Community Forum
Running code in debug mode is a lot slower than executing normally - is it possible to improve execution speed?. I've attached example...
Read more >UVISION DEBUGGER: Maximize Simulation Speed
QUESTION. How can I maximize the simulation speed of the µVision Simulator? ... The option Project - Debug - Limit Speed to Real-Time...
Read more >Optimize your build speed | Android Developers
This page provides some techniques to help resolve build speed bottlenecks. The general process of improving your app's build speed is as follows:....
Read more >How to improve speed of debugging in powershell
The debugging experience won't be nowhere near as nice, but you can try console-based debugging via Set-PSBreakpoint to see if that is faster....
Read more >Improve Android and iOS debug compilation speed - grijjy blog
The majority of time compiling a Debug build is spent creating debug information, so this is where gains can be made. Making just...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Nice catch, @pmcharrison. This function should be updated to also use
ExperimentFileSource
, like theverify_directory
function above it. I think this would fix the problem.…but one possibility would be to set a lower value of
threads
solely in debug mode?