Explore >> Select a destination
|
You are here 
|
healeycodes.com | ||
| | | | |
blog.valentin.sh
|
|
| | | | | [AI summary] The author analyzes the performance of a command-line todo program, identifying that the majority of the execution time is due to Python interpreter startup and standard library imports, rather than their own code. | |
| | | | |
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. | |
| | | | |
nelari.us
|
|
| | | A look at the most notable challenges in implementing Peter Shirley's Raytracing In One Weekend using wgpu and WGSL. | ||
