[ https://issues.apache.org/jira/browse/AIRFLOW-1483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Edgar Rodriguez updated AIRFLOW-1483: ------------------------------------- Description: The current hardcoded values for the {{page_size}} on {{AirflowModelView}} is set to {{500}} rows, which is usually too large to render in less than 1-2 secs in modern browsers. Also, in some endpoints it is also taking a long time to render server-side the HTML content for 500 rows, taking around 1-2 secs (on the server) or sometimes more. Simple approach is to reduce this value to something more sensible (100 maybe?). Probably making it a configurable value would be a good option too in case the default is not good enough. See attachment for a profiled sample of a page loading time. was: The current hardcoded values for the {{page_size}} on {{AirflowModelView}} is set to {{500}} rows, which is usually too large to render in less than 1-2 secs in modern browsers. Also, in some endpoints it is also taking a long time to render server-side the HTML content for 500 rows, taking around 1-2 secs (on the server) or sometimes more. Simple approach is to reduce this value to something more sensible (100 maybe?). Probably making it a configurable value would be a good option too in case the default is not good enough. > Page size on model views is to large to render quickly > ------------------------------------------------------ > > Key: AIRFLOW-1483 > URL: https://issues.apache.org/jira/browse/AIRFLOW-1483 > Project: Apache Airflow > Issue Type: Bug > Reporter: Edgar Rodriguez > Assignee: Edgar Rodriguez > Attachments: taskinstance_page_loading_breakdown.png > > > The current hardcoded values for the {{page_size}} on {{AirflowModelView}} is > set to {{500}} rows, which is usually too large to render in less than 1-2 > secs in modern browsers. > Also, in some endpoints it is also taking a long time to render server-side > the HTML content for 500 rows, taking around 1-2 secs (on the server) or > sometimes more. > Simple approach is to reduce this value to something more sensible (100 > maybe?). Probably making it a configurable value would be a good option too > in case the default is not good enough. > See attachment for a profiled sample of a page loading time. -- This message was sent by Atlassian JIRA (v6.4.14#64029)