Hello,
my apologies for the inappropriate questions.
I'll file an issue when it's needed.
Best Regards,
Giorgio.

Il giorno mar 1 feb 2022 alle ore 22:38 Jarek Potiuk <ja...@potiuk.com> ha
scritto:

> I think this is not the best place to ask those kinds of questions. Please
> open a slack question or Github Discussions if you want to discuss "using"
> of airflow. All links here: https://airflow.apache.org/community/
>
> Also - if I may suggest you - you asked a very imprecise question and you
> are unlikely to get any answer. in your future (I hope) Github
> Discussion/Slack query you should be much more precise. I suggest you
> answer yourself first:
>
> * What does it mean "a lot"?
> * Why do you think it is "too much"?
> * Did you check how much your code is consuming?
>
> The python will consume as much memory as much of the code you run so
> memory consumption is something that very much depends on the code you
> write. So I would revert the question (and please be prepared before you
> ask the question) - what did you do to measure the memory used by your
> code? How much your code uses out of the "lot" memory use?
>
> If you answer the questions to yourself - and make a more detailed and
> precise question, you are likely to get answers (but not before).
>
> Also you should rather refrain from asking multiple questions in one
> thread. I propose you open separate threads for each of the questions you
> have (in Github Discussions) this is a much more efficient way of asking
> for help. But Again DevList is likely not the best place to ask those
> questions.
>
> J
>
>
> On Tue, Feb 1, 2022 at 8:42 PM Giorgio Zoppi <giorgio.zo...@gmail.com>
> wrote:
>
>> Hi devs,
>> I have tried multiple LocalExecutors in 16GB vm and sometimes
>> I have experienced workers consuming a lot of memory, Is this normal?
>> Is there any incoming activity to improve worker performance for python
>> operators?
>> Is there any java/go operator available?
>> Best Regards,
>> Giorgio
>>
>>
>>
>>

-- 
Life is a chess game - Anonymous.

Reply via email to