Bisaloo
commented
6 months ago Thanks for the report! I agree this would be desirable.
It needs to be followed by a series of performance improvements to avoid any unnecessary resource consumption if we increase the frequency.
My main unresolved question at the moment is how to consider historical data saving in this. Should we still save all occurrences (related to #52)? Or keep every hour with, e.g., a counter that will only save historical data every other or fourth run? :thinking:
Currently, the CRAN incoming FTP server is polled once an hour:
https://github.com/r-hub/cransays/blob/b0cc818c69ebf389cc2f1122e3141ac5da19d93d/.github/workflows/render-dashboard.yml#L10-L11
Have you considered increasing this to, say, two or four times an hour? I doubt it would make a big dent in the total amount of traffic that the CRAN server sees. It might even help decrease the traffic by moving someone who's tracking their package manually to looking at CRANsays instead - once an hour is not enough for such use.
UPDATE: I see that https://nx10.github.io/cransubs/ is updated once every ten minutes. UPDATE 2: It's updated only when someone access it, and I guess at most every 10 minutes.