You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the problem to be solved
When the OpenAPI gets very large (190K+ lines of code in the OpenAPI), it causes Redoc performance to drop significantly. In average consumes 1.2GB of the browser's memory and it took 1.2 minute for the First Contentful Paint (FCP).
Describe the solution you'd like
One of the potential solutions I analyzed is Virtualization. Currently it would render the whole HTML page, which is quite good for small OpenAPIs, but could hurt huge API specifications.
By having Virtualization, I believe it will improve Redoc significantly on larger API Documentations as the browser will only render what is currently user is seeing.
Of course not everyone would like to have Virtualization. So perhaps adding it as one of the configuration options will help.
Thank you very much!
The text was updated successfully, but these errors were encountered:
Describe the problem to be solved
When the OpenAPI gets very large (190K+ lines of code in the OpenAPI), it causes Redoc performance to drop significantly. In average consumes 1.2GB of the browser's memory and it took 1.2 minute for the First Contentful Paint (FCP).
Describe the solution you'd like
One of the potential solutions I analyzed is Virtualization. Currently it would render the whole HTML page, which is quite good for small OpenAPIs, but could hurt huge API specifications.
By having Virtualization, I believe it will improve Redoc significantly on larger API Documentations as the browser will only render what is currently user is seeing.
Of course not everyone would like to have Virtualization. So perhaps adding it as one of the configuration options will help.
Thank you very much!
The text was updated successfully, but these errors were encountered: