You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please correct me if this is due to my insufficient python3/asyncio skills, but it seems like the new python-async version is much slower than the previous synchronized one.
A quick test (values are means of some iterations, the r2 specific cmd doesn't matter):
$ python3 --version
Python 3.5.3
Synchronous version (version 2.4.0 commit 007f1d6):
That's a performance detoriation by roughly factor 300 per r2 command. As I see it there is currently no way to fall back to the synchronous version in 2.8.0 (apart from messing with the python version). Would it be possible to bring back the synchronous version for python3 (or enlighten me what I am doing wrong here)?
The text was updated successfully, but these errors were encountered:
Please correct me if this is due to my insufficient python3/asyncio skills, but it seems like the new python-async version is much slower than the previous synchronized one.
A quick test (values are means of some iterations, the r2 specific cmd doesn't matter):
Synchronous version (version 2.4.0 commit 007f1d6):
7.534199903602712e-05
Asynchronous version (version 2.8.0, commit 6f60dee):
0.023162505000072997
That's a performance detoriation by roughly factor 300 per r2 command. As I see it there is currently no way to fall back to the synchronous version in 2.8.0 (apart from messing with the python version). Would it be possible to bring back the synchronous version for python3 (or enlighten me what I am doing wrong here)?
The text was updated successfully, but these errors were encountered: