APScheduler + requests 遇到 OSError: [Errno 24] Too many open files 的問題
#apscheduler #bug #code #collection #flask #gc #gunicorn #pypy #pypy3 #python #requests #source #urllib #urllib3 #workaround
APScheduler + requests 遇到 OSError: [Errno 24] Too many open files 的問題
#apscheduler #bug #code #collection #flask #gc #gunicorn #pypy #pypy3 #python #requests #source #urllib #urllib3 #workaround
Wrzuciłem dzisiaj nową weresję #PyPy3.10 do #Gentoo, która poprawia, ekhm, "iterację po współprogramach przy pomocy API rozszerzeń C". Albo, mówiąc prościej, naprawia rozszerzenie yajl2_c w paczce ijson.
Chciałbym z całego serca podziękować rtobar za włożenie wielkiego wysiłku, by rozkminić ten problem, naprawić PyPy i przy okazji poprawić kilka innych problemów po stronie ijson. Naprawdę taką współpracę chciałbym widywać codziennie!
https://github.com/ICRAR/ijson/issues/101
https://foss.heptapod.net/pypy/pypy/-/issues/3956
I've pushed a new #PyPy3.10 build to #Gentoo today with a fix for, err, "iterating over coroutines in C extension API". Or, to put it simpler, it fixes problems with yajl2_c extension in ijson.
I'd like to wholeheartedly thank rtobar for going above and beyond the call of duty, figuring out where the problem is, fixing PyPy and making a bunch of fixes to ijson as well. This is really awesome kind of interaction I'd love to see every day!
https://github.com/ICRAR/ijson/issues/101
https://foss.heptapod.net/pypy/pypy/-/issues/3956
I've done a benchmark between Rust, C, Common Lisp and Python on my SBC which has ARM processor and here are the results:
https://far.chickenkiller.com/computer/benchmarking-common-lisp-rust-c-and-python-on-arm/
#benchmark #c #lisp #cl #common_lisp #rustlang #arm #armv7 #pi #python #cpython #pypy #pypy3
I have previously benchmarked C++ against Common Lisp and the result was that unlike the common belief about Lisp, it can have performance which is almost as fast as C++. After that I did another benchmark for computing fibonnaci series using Rust, Common Lisp, C and Python. But both of these benchmarks were done on x86_64. In this benchmark, I’m using the same codes from the last benchmark but run them on an ARM device instead. Unfortunately, my device is old and not ARM64 but still it can be of interest.