Packages take a long time to become visible to conda search after upload #13
Replies: 3 comments 2 replies
-
Update: this package became available around about 0729 PST (December 10), so approximately 75 minutes after being uploaded. |
Beta Was this translation helpful? Give feedback.
-
Packages that are uploaded to That said, it is typically closer to ~30mins. 75mins does sound a bit long. @chenghlee do you have any thoughts here? |
Beta Was this translation helpful? Give feedback.
-
Digging through the logs on the sync worker, since 2021-09, each CDN sync run now takes ~47 minutes; about 60% of that time (~28 min) is spent running These numbers seem to be mostly independent of the number of packages being synced, so there's definitely something a little to a lot weird going on. I've opened a ticket with Anaconda's Infrastructure team to take a look at what's going on, though given the time of year, we may not have a real answer until Q1 of next year. |
Beta Was this translation helpful? Give feedback.
-
I regularly see that packages that get uploaded to https://anaconda.org/conda-forge take ~1 hour or more (as timed by the Uploaded timestamp on the
/files
page for that package) to become visible withconda search
. Is there an way to more regularly update the package list (repodata?) for a channel to have packages become usable with a lower latency?My current example is
osx-64/python-lalburst-1.5.9-py310h93fb10b_2.tar.bz2
which was Uploaded '1 hour and 6 minutes ago' bycf-staging
, but isn't available fromconda search
Is there anything that I ('the user') can do to speed things up?
Beta Was this translation helpful? Give feedback.
All reactions