When the front-end calls ListAPIProducts method the response time is lower each time.
First time takes around 30 seconds. After 6 times, it takes less than 3 ms.
Having the first call taking more than 30 seconds, it is too much.
Here some screenshots of the logs
To help on reproducing the scenario:
The APIDocs containing the swagger specs are stored in configmaps
The APIProducts are 10. Each of them pointing to 1 APIDoc.
The number of operations in the swagger specs are, for those 10 products, as follows:
9, 10, 5, 14, 10, 35, 35, 16, 2, 10
Making a total of 146 operations which are added to the status of the resources.
The pods (proxy and portal controller) were deployed in the same kubernetes node.
Thank you
To get an example of the heavy swagger spec used for this scenario, please, contact @antonioberben
portal version 1.1.1 gloo edge version 1.9.0
When the front-end calls
ListAPIProducts
method the response time is lower each time.First time takes around 30 seconds. After 6 times, it takes less than 3 ms.
Having the first call taking more than 30 seconds, it is too much.
Here some screenshots of the logs
To help on reproducing the scenario:
The APIDocs containing the swagger specs are stored in configmaps The APIProducts are 10. Each of them pointing to 1 APIDoc. The number of operations in the swagger specs are, for those 10 products, as follows: 9, 10, 5, 14, 10, 35, 35, 16, 2, 10 Making a total of 146 operations which are added to the status of the resources.
The pods (proxy and portal controller) were deployed in the same kubernetes node.
Thank you
To get an example of the heavy swagger spec used for this scenario, please, contact @antonioberben