potiuk commented on issue #57776: URL: https://github.com/apache/airflow/issues/57776#issuecomment-3700086640
Not sure why you are tagging me, but generally issues are solved and tackled when someone works on them. It can be anyone - including you - who might take a look at the issue. I believe there is a continuous effort to improve things (as you can see from 3.1.0 -> 3.1.5 improvements, there is 3.1.6 in the making and different people work on different parts - and there is no single person that can be asked for "plans" as there are about 100 independent people a month working on their own. Generally, the best thing you can do is to make as much as possible diagnosing and posting your case - short of providing a fix yourself, this is likely the best way of addressing things - for example you can use memray to analyse the memory issues or logging the database queries you see and looking at them and provide more information. This, rather than asking for plans, is the best way to speed up things. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
