Danny Kulchinsky

> I think it is a worthwhile addition but will not fit in 2.7 unless someone in the community volunteers to work on it. that's a shame, according to @OrlinVasilev...

> It was flagged as a 2.7 candidate, not as a commitment. The 2.7 development window is shorter than usual because of China and US holiday closures during this period...

> Could you check the jobservice logs? I did, and can't find anything of relevance. unless you can tell me.what to look for? perhaps I'm missing something

@chlins combed through the jobservice logs again and found this: ``` 2022-09-14T20:36:56Z [INFO] [/jobservice/worker/cworker/reaper.go:181]: Reaper: mark job 4746d1529505908316d7f391 failed as job is still not finished in 1 day ``` `4746d1529505908316d7f391`...

> It seems that the name of job_logger is invalid, see the sample configure, only support "FILE" and "STD_OUTPUT" Hi, @stonezdj This is strange, we've used DB job loggers since...

> Could you provide the `ListRepositories` API details includes query parameters? Hey @chlins 👋🏼 the query param is `/projects//repositories`

Hey @chlins any thoughts on this? is this an expected degradation between 2.3.3 & 2.5.3 for this API?

> Hi, @dkulchinsky, from harbor previous performance report(https://github.com/goharbor/perf/wiki) the result shows there is no degradation for this API between 2.3.x & 2.5.x Looking at this, it's not representative of our...

> I think you could open the postgres monitor if you have or enable the pg statements(FYI: [postgresql.org/docs/current/pgstatstatements.html](https://www.postgresql.org/docs/current/pgstatstatements.html)), then run the list repositories continuously, and fetch the slowest query. Thanks...

> @dkulchinsky Hi, I think the issue may occur when the project with big number of repositories and artifacts, this API performance downgrade may be brought by some code changes...