[issue26284] Fix telco benchmark

STINNER Victor added the comment: Sorry, I'm not sure if you want to make any change to bm_telco.py of the performance. If yes, please open an issue at https://github.com/python/performance > So LGTM. Hum, it looks like you are happy, so I now close this issue :-) I'm slowly trying to move

[issue26284] Fix telco benchmark

Stefan Krah added the comment: Wow, on my machine this is very stable, great. The output should be like http://www.bytereef.org/software/mpdecimal/benchmarks/telco.py , but printing one number only should be okay. The important thing is that some decimal is printed at all to test the

[issue26284] Fix telco benchmark

STINNER Victor added the comment: @Stefan: Can you please check bm_telco.py and maybe propose a pull request if something is wrong? -- ___ Python tracker

[issue26284] Fix telco benchmark

STINNER Victor added the comment: I worked on a new version of the benchmark suite, it is now called performance and moved to GitHub: https://github.com/python/performance In performance 0.1.2, bm_telco.py uses BytesIO for input and six.StringIO for output. The output is just one number per

[issue26284] Fix telco benchmark

STINNER Victor added the comment: > Unfortunately, replacing io.BytesIO(data) with indexing does not make the > benchmark faster or more stable on my machine. Ah, I didn't check. I expected BytesIO.read() to be slower than bytes string slicing. --

[issue26284] Fix telco benchmark

Brett Cannon added the comment: If you think the string conversion should go back in, Stefan, feel free to put it back (unless Victor wants to say why he took it out). -- assignee: -> skrah ___ Python tracker

[issue26284] FIx telco benchmark

Stefan Krah added the comment: Unfortunately, replacing io.BytesIO(data) with indexing does not make the benchmark faster or more stable on my machine. BTW, string conversion of the result is actually a crucial part of the benchmark, it was taken out in

[issue26284] Fix telco benchmark

Changes by Stefan Krah : -- title: FIx telco benchmark -> Fix telco benchmark ___ Python tracker ___

[issue26284] FIx telco benchmark

New submission from Stefan Krah: The telco benchmark is unstable. It needs some of Victor's changes from #26275 and probably a larger data set: http://speleotrove.com/decimal/expon180-1e6b.zip is too big for _pydecimal, but the one that is used is probably too small for _decimal. --