mcatanzaro wrote: > I started testing the staging server yesterday. It seems a little slow > -- I worry for anyone debugging anything that links to WebKit, which > on the desktop is a lot -- but otherwise it works *very* well. I'm > impressed. Very nice. It'd be good to get a sense of what you found slow. The .stg. server is just finishing up ingesting all the koji rpms, so has been fully occupied with that. In the case where a new file is sought from inside some large rpm, yeah there will be some inherent latency in decompressing it (CPU bound), saving the selected file to tmp disk (RAM/storage bound) and then sending you the file (network bound). At the server, there are some prefetching/caching options available to take advantage of the spacious servers kindly provided by fedora-infra. There is also aggressive caching on the client side, with an adjustable week-long retention for files. See the CACHE section in [man debuginfod_find_debuginfo]. Plus web caching proxies or federated intermediate debuginfod servers can add site-level caching near you. - FChE _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
