potiuk commented on PR #63:
URL: https://github.com/apache/airflow-ci-infra/pull/63#issuecomment-1827636172

   I've run a few builds with `debug-ci-resources` turned on and this one was 
the biggest tmpfs usage I could find:
   
   * 
https://github.com/apache/airflow/actions/runs/7003593564/job/19050346759#step:7:1589
   
   
   
![image](https://github.com/apache/airflow-ci-infra/assets/595491/6fbc2112-9983-4150-a8f8-4fe0a8127056)
   
   
   I think we can safely give our tests ~10% memory. 
   
   Actually - I am not even  sure if it will change anything (I believe when 
tmpfs capacity is set, it will use only as much as it actually uses, it does 
not reserve it, it's just the maximum it will use. 
   
   So I am not even sure if we should merge it. I just wanted to start 
potentially a discussion if we want to do some optimisations there (and show 
@hussein-awala the nice resource debugging feature we have by assigning 
'debug-ci-resources` label. 
   
   BTW. We are discussing with datadog a possibilit of them donating us CI 
Datadog monitoring solution that we could plug-in instead of those 
"do-it-yourself" monitoring we have :)
   


-- 
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]

Reply via email to