As of 2-nov-2022, there is a hardcoded CRONJOB_SYNC_INTERVAL_SECONDS that triggers miner_sync_simple.rb followed by analytics.
There is no separate interval that triggers just analytics.
Kotenok2000 wants a configurable interval for only analytics.
Analytics generates histograms, populates bloomfilters.
Here newly discovered programs affects the stats.
This is time consuming, so it's not something we want to happen for every discovered program.
Doing a miner_sync_simple.rs causes network traffic, and invalidates the analytics. This is time consuming.
Extend the config.toml with 2 parameters: miner_sync_interval=24h and analytics_interval=1h.
This can help finding a sweet spot.
As of 2-nov-2022, there is a hardcoded
CRONJOB_SYNC_INTERVAL_SECONDSthat triggersminer_sync_simple.rbfollowed byanalytics.There is no separate interval that triggers just analytics.
Kotenok2000 wants a configurable interval for only
analytics.Analytics generates histograms, populates bloomfilters.
Here newly discovered programs affects the stats.
This is time consuming, so it's not something we want to happen for every discovered program.
Doing a
miner_sync_simple.rscauses network traffic, and invalidates the analytics. This is time consuming.Extend the
config.tomlwith 2 parameters:miner_sync_interval=24handanalytics_interval=1h.This can help finding a sweet spot.