Profiling Python in Production

Re:Profiling Python in Production by sitkack on Wednesday December 30, 2015 @06:02AM (#10811618)

Reducing CPU load also

* reduces power usage, wear and tear on hardware

* gives more capacity for traffic surges

* gives more headroom for new features

* enables running on a smaller instance

This isn't an argument against slow code, more of a suggestion to tune out unnecessary work.

[ Parent | on HN ]

Re:Profiling Python in Production by valarauca1 on Wednesday December 30, 2015 @06:31AM (#10811677)

Slow code is just paying for developer productivity in CPU time instead of labor time.

It's great in theory until the AWS bill arrives. Often times it's still fine, just depends where the bottom line is.

[ Parent | on HN ]

Re:Profiling Python in Production by sitkack on Wednesday December 30, 2015 @07:22AM (#10811787)

Agreed, I love slow interpreted languages like Python and writing _fast_ Python is a different kind of optimization that one would do C. In cases like the article, the biggest gains are in just not doing something, or doing it less often.

[ Parent | on HN ]

Re:Profiling Python in Production by nitin_flanker on Wednesday December 30, 2015 @07:20AM (#10811781)

This also ahead reduces the maintenance time and efforts which ahead increase productivity. Overall they did a great job.

[ Parent | on HN ]

Re:Profiling Python in Production by Walkman on Wednesday December 30, 2015 @10:20AM (#10812358)

That might not be True for optimizations, because optimized code is usually less readable.

[ Parent | on HN ]