Hacker News

points by nrawe 2 days ago | 0 comments

Doing it currently, Python to Go. Early indications are a 50-98% increase in speed (e.g. one testcase went from 26hrs to 30mins) for network/CPU heavy workload. Conversion via Qwem, lots of testing needed but compute savings will be worth it.

[–] mynegation 2 days ago

Did you mean “50-98% decrease in running time”? Just calculating from your 26hrs to 30 mins seems to imply so. In terms of speed that translates to 100% to 5100% increase in speed.

[–] nrawe 1 day ago

Yes, sorry, typing fast - we knew Go would be faster but not quite on that scale.

[–] mcepl 1 day ago

Where you using standard optimized libraries (e.g., NumPy for numerical computation) or did you do everything in Python? This kind of increase of speed seems to indicate extremely sloppy Python programming.

[–] gf000 2 days ago

Why not go with something like graalpy first? That's much less risk in terms of "we end up slightly changing behavior"

[–] nrawe 1 day ago

It's the same level of testing for us for either Python2->3 or Go (it's a legacy code base, low automated coverage).

Conversion is now (somewhat) easier, the testing will be the slow part. For the speed improvements, which we also need for a migration from on-prem to cloud, it's a no brainer vs the other options at our disposal (like GraalPy).