You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At #277, @ajeanmahoney requests that the RFC dataset be updated at least once every 12 hours. I'm wondering if the community will want the updates to appear even more rapidly, and suggest we look at the cost of an update once per hour.
We should tune this for all the datatasets.
Is there a quick link to point to what the current configuration is?
The text was updated successfully, but these errors were encountered:
The delay, if any, is configured in environment variables (Kesara may know the value, I believe he mentioned it’s 1 day)
Having a source reindexed more often than it is rebuilt (specified in GHA) will not provide any improvement.
A data source should be rebuild more frequently first, and then reindexing can be made more frequent.
Bulk-indexable sources are generally not designed to provide near-real-time availability. For realtime availability it’s more appropriate to configure an external source for RFCs, the way individual I-Ds are retrieved from Datatracker or DOIs from Crossref. (See docs for the distinction between external and indexable bibliographic data sources.)
@strogonoff is exactly right. Other than those considerations, we also want to make sure that overlapping fetching and indexing processes don't happen simultaneously.
At #277, @ajeanmahoney requests that the RFC dataset be updated at least once every 12 hours. I'm wondering if the community will want the updates to appear even more rapidly, and suggest we look at the cost of an update once per hour.
We should tune this for all the datatasets.
Is there a quick link to point to what the current configuration is?
The text was updated successfully, but these errors were encountered: