API PRD server was lagging for load time, which might need to be optimized at load balancing, according to @taylordm .
The lagging might be caused by high request rates, after MTP portal https://moleculartargets.ccdi.cancer.gov/ was publicly released, as MTP portal sends HTTP requests to API PRD server to get plots, according to @chinwallaa .
@chinwallaa suggested to check the usage stats of API PRD server, which can be estimated using API DEV server log.
@brianghig suggested to check the AWS monitoring stats to see whether the API PRD server is hitting limits on CPU, RAM, or Disk I/O.
I will check server log and AWS monitoring stats according to the suggestions of @chinwallaa and @brianghig .
cc @blackdenc
API PRD server was lagging for load time, which might need to be optimized at load balancing, according to @taylordm .
The lagging might be caused by high request rates, after MTP portal https://moleculartargets.ccdi.cancer.gov/ was publicly released, as MTP portal sends HTTP requests to API PRD server to get plots, according to @chinwallaa .
@chinwallaa suggested to check the usage stats of API PRD server, which can be estimated using API DEV server log.
@brianghig suggested to check the AWS monitoring stats to see whether the API PRD server is hitting limits on CPU, RAM, or Disk I/O.
I will check server log and AWS monitoring stats according to the suggestions of @chinwallaa and @brianghig .
cc @blackdenc