Explore >> Select a destination
|
You are here 
|
healeycodes.com | ||
| | | | |
hypothesis.works
|
|
| | | | | Testing performance optimizations Once you've flushed out the basic crashing bugs in your code, you're going to want to look for more interesting things to test. The next easiest thing to test is code where you know what the right answer is for every input. Obviously in theory you think you know what the right answer is - you can just run the code. That's not very helpful though, as that's the answer you're trying to verify. But sometimes there is more than one way to get the right answer, and you choose the one you run in production not because it gives a different answer but because it gives the same answer faster. Test faster, fix more | |
| | | | |
ehmatthes.com
|
|
| | | | | I was working on a longer post recently about optimizing a messy exploratory Python project, where the file I was focusing on took about 16 seconds to run. | |
| | | | |
adamj.eu
|
|
| | | | | When trying to improve a slow function or module, it's always a good idea to profile it. Here's a snippet for quickly profiling a section of code with Python's cProfile module, in two flavours. It's adapted from the cProfile documentation's Profile example. I have used versions of this snippet over the years to narrow in on performance issues. | |
| | | | |
www.buildahomelab.com
|
|
| | | How to Install Ansible with pipenv and pyenv. Pipenv gives a lot of flexibility over ansible project versioning. | ||
