potiuk commented on issue #37131: URL: https://github.com/apache/airflow/issues/37131#issuecomment-1946571845
Out-of-the-box: one other option (but this one sounds almost too invasive) is to perform additional fork instead of a deep-copying the objects. Sounds counter-intuitive, but forks are fast and relatively inexpensive and forked processes use copy-on-write, so they use almost no extra memory. Seems that the objects we are copying are relatively complex and expensive to copy in python code, but copy-on-write are cloning the whole segments of written memory so when the objects get modified in the fork, they copy-on-write will be way faster. -- 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]
