RetroSearch Browse

Mon Mar 26 01:03:46 CEST 2012 · https://mail.python.org/pipermail/python-dev/2012-March/118106.html

> The 80x is a ballpark figure for the maximum expected speedup for
> standard numerical floating point applications.

Ok, but it's just surprising when you read the What's New document.
72x and 80x look to be inconsistent.

> For huge numbers _decimal is also faster than int:
>
> factorial(1000000):
>
> _decimal, calculation time: 6.844487905502319
> _decimal, tostr():          0.033592939376831055
>
> int, calculation time: 17.96010398864746
> int, tostr(): ... still running ...

Hum, with a resolution able to store the result with all digits? If
yes, would it be possible to reuse the multiply algorithm of _decimal
(and maybe of other functions) for int? Or does it depend heavily on
_decimal internal structures?

Victor

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2012-March/118106.html below:

[Python-Dev] [Python-checkins] cpython: Issue #7652: Integrate the decimal floating point libmpdec library to speed