sbp commented on issue #816: URL: https://github.com/apache/tooling-trusted-releases/issues/816#issuecomment-4970216803
After a week of collecting statistics on `atr-staging`, we recorded a maximum of 992 MiB RSS for the server process. It was a peak for under five minutes. The maximum number of file descriptors was 49. The gauge maximum for the workers was 212 MiB, but the `rusage` tracker shows that one peaked at 469 MiB. Worker peak queue depth was 28, apparently caused by many simultaneous RAT checks. The RAT checks take 27s on average, with a worst case of 57s. The worst task overall was actually a license headers check, at 64s. The slowest archive extraction was only 4.5s. 2 GB for the server, plus 0.5 GB * N workers, plus 0.5-1 GB for the database should be sufficient for the core processes. For 4 workers that would be 4.5-5 GB, and for 8 workers 6.5-7 GB. We are likely to have other processes on there, however, such as monitoring, the backup systems, etc. Again the statistics show that the recurring tasks should either be pruned, or perhaps recorded only to a log, as they form the vast majority of new database rows and yet are of very marginal value to retain. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
