NFR Test Results for NGF version edge

[github-actions]

Update with NFR test results for NGF version edge ["oss","plus"]

• Auto-generated by the NFR tests workflow run 17568230708
• Tests ran using Docker image tag edge
• scale test(s) ran

[sjberman]

Overall seeing some increases in latency and memory usage. Also quite a few error logs for conflicting status updates and no live upstreams.

[bjee19]

Though something to note is the edge results are from March 2025, about 6 months ago.

Also I just realized, annoyingly, files that didn't get generated, don't get removed from the edge results. So for example in the scale/edge/TestScale_UpstreamServers/ngf-plus.log there are logs from october 2024, since past then that were no ngf error logs so that file never got generated. But this bot doesn't remove the file. @sjberman think this could be a possible improvement to the nfr workflow?

[salonichf5]

Though something to note is the edge results are from March 2025, about 6 months ago.

Also I just realized, annoyingly, files that didn't get generated, don't get removed from the edge results. So for example in the scale/edge/TestScale_UpstreamServers/ngf-plus.log there are logs from october 2024, since past then that were no ngf error logs so that file never got generated. But this bot doesn't remove the file. @sjberman think this could be a possible improvement to the nfr workflow?

Yes I saw that too, if nothing gets generated they don't get overwritten.

I was just discussing things @sjberman offline, he recommended we take note of CPU usage and memory for NGINX pods as well. We only do it for NGF now. So I was going to open a story for that, i'll add this in the acceptance criteria too since we need to make sure we get updated results.

[sjberman]

@bjee19 Yeah we should probably have some automation to clean those up. For now, we should just manually remove what isn't needed.