Недавно делал быстрый прототип асинхронного приложения в котором требовалось вызывать много синхронного кода. Да, я знаю, что это не лучший дизайн, но нужно было быстрое решение на один процесс и без очередей. Поэтому я выполнял код в потоках.
Выглядело это примерно так:
from fastapi.concurrency import run_in_threadpool
async def execute(data: DataRequest) -> DataResponse:
try:
result = await run_in_threadpool(sync_function, data)
return DataResponse(data=result)
except Exception as e:
return DataResponse(
error=str(e),
success=False,
)
В общем работает нормально. Для всех вызовов под капотом используется общий тредпул, всё работает предсказуемо.
Но потребовалось изменить количество запускаемых в пуле потоков (по умолчанию создается 40 воркеров).
Так как дело происходит с FastAPI, делается это через lifespan используя настройки anyio:
import anyio
@asynccontextmanager
async def lifespan(app: FastAPI):
limiter = anyio.to_thread.current_default_thread_limiter()
limiter.total_tokens = 100
yield
# если вдруг нужно вернуть обратно
limiter.total_tokens = 40
Зачем менять количество воркеров?
- уменьшить, если оперативки мало (один тред занимает ~8мб)
- увеличить чтобы выдержать нагрузку
Если есть предложения получше при тех же вводных - предлагайте😉
#async
⚡ Jerome Powell (Chairman of the Fed):
✔ There is no recession in the USA.
❗️We may see inflation turn out to be lower than expected, in which case we would consider a Fed rate cut.
✔ A weakening labor market also suggests a faster rate cut.
✔ The Fed predicts that inflation will rise due to tariffs.
✔ Most Fed members believe it would be appropriate to cut rates later this year.
✔ So far, there are no conflicts between the Fed's dual mandates (labor market and inflation).
✔ The Fed's policy will not trigger an increase in housing supply in the long term.
❗️Banks are free to provide services to the crypto industry and conduct their activities, provided they ensure safety and reliability.
✔ I'm not worried about the latest macroeconomic data, but I am concerned about how it might change.
✔ We expect inflation to rise due to tariffs, but we do not yet know the extent of its impact on consumers. Therefore, we must wait.
✔ As long as the economy remains strong, we can afford to take a short pause.
❗️We will lower the Fed rate when the time is right.
✔ I think inflation will start to rise due to tariffs beginning in June.
✔ We will monitor the situation throughout the summer.
✔ There is no need to rush.
✔ I will not name a specific month in which we might cut the Fed rate.
✔ The Fed is simply trying to act cautiously and prudently.
✔ Economic growth will slow down this year. Immigration is one of the reasons.
✔ The dollar will remain a reserve currency for a long time.
✔ The US government bond market is functioning normally.
❗️The Fed will not tighten monetary policy or adjust the rate just because of rising oil prices. We will evaluate the entire macroeconomic picture.
✔ The dollar will remain a reserve currency for a long time.
✔ The US government bond market is functioning normally.
❗️The Fed will not tighten monetary policy or adjust the rate just because of rising oil prices. We will evaluate the entire macroeconomic picture.
✔ We are approaching price stability, but we have not quite achieved it yet.
❗️ The Fed does not have the right to buy cryptocurrency on its balance sheet and we do not seek to do so.
❗️Phs will continue to reduce balance ( #QT ).
✔ Small business lending conditions are a bit strict.
✔ We expect to see the impact of Trump's tariffs on inflation this summer.
❗️If this does not happen, we will lower the rate .
✔ We are currently in watch and wait mode.
✔ Overall, the inflation picture is quite positive.
J. Powell testifies before the House Financial Services Committee on Monetary Policy.
https://groups.google.com/forum/#!topic/pyside-dev/pqwzngAGLWE
Dear #Pyside2 contributors,
As you might know, Pyside was originally developed for Nokia while it was the owner of the #Qt technology. When Nokia sold Qt to Digia (and now The Qt Company), all the copyrights over the original Pyside code for Qt 4 got transferred to The Qt Company as well.
For different reasons, it was not possible for The Qt Company to push Pyside forward as much as we would have wished over the last few years. Fortunately this changed now, and The Qt Company is today in a position, where it can and will invest into Pyside. The goal is to ensure Pyside becomes a fully supported part of the Qt product family, with a similar development and licensing model as the rest of Qt. We want to make sure Pyside works on new Qt releases when they come out and are committed to invest long term into the technology.
A clone of Media Player Classic reimplemented in Qt for Windows desktop. It aims to reproduce most of the interface and functionality of mpc-hc while using libmpv to play video instead of DirectShow.
https://github.com/mpc-qt/mpc-qt
#windows#media#Qt
https://wiki.python.org/moin/PyQt
#PyQt is one of the two most popular Python bindings for the #Qt cross-platform #GUI/#XML/#SQL#C++ framework (another binding is #PySide).