I've been profiling the web UI for the last few days and I think I've been able to identify some of the issues. I've seen similar response times from the webserver. A couple of things that I found specifically for the task instance view are: 1. Page sizes on views are usually too large, and all HTML rendering is done server side, flask_admin introduces some latency rendering the templates for 500 TIs at a time in the TaskInstanceModelView, see [ AIRFLOW-1483 <https://issues.apache.org/jira/browse/AIRFLOW-1483>] 2. Using unindexed column as default for ordering (required for paging), triggering a sort on TI requests, e.g. TaskInstanceModelView uses `job_id` as default sort column, but there's no index for that, see [AIRFLOW-1495 <https://issues.apache.org/jira/browse/AIRFLOW-1495>]
Cheers, Edgar On Tue, Aug 8, 2017 at 11:56 AM, Victor Monteiro <victor.monte...@ubee.in> wrote: > Sorry, I am sending again. > > Also, it is always between 6s and 3s. > > > Em ter, 8 de ago de 2017 às 15:21, Ash Berlin-Taylor < > ash_airflowl...@firemirror.com> escreveu: > >> (Your screenshot didn't come through for me, possibly because the list >> stripped it? That said:) >> >> Is it always 6 seconds, or after making a few requests, enough so that >> each worker stands a chance to have loaded the app any deps does it settle >> down? >> >> i.e. the problem might just be that of warm-up. >> >> -ash >> > On 8 Aug 2017, at 18:52, Victor Monteiro <victor.monte...@ubee.in> >> wrote: >> > >> > Hi everyone. >> > >> > The problem is very straightforward. When doing a request to airflow >> webserver, it is taking too much time to send the first byte. >> > >> > >> > >> > As you can see in the picture, it took 6 seconds to send the first >> byte. I already investigated the connection with the database and it took >> 36ms to list all task instances. So, I am starting to think there is a >> problem with airflow webserver or my deployment. >> > >> > To give you more details about deployment and configurations: >> > web_server_worker_timeout = 120 >> > workers = 4 >> > sql_alchemy_pool_size = 5 >> > sql_alchemy_pool_recycle = 3600 >> > AWS RDS postgres >> > AWS m4.large >> > Does anyone know what can be causing this problem? >> > >> > Thank you :D >> > >> >>
