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
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.
The text was updated successfully, but these errors were encountered:
As of 2-nov-2022, there is a hardcoded
CRONJOB_SYNC_INTERVAL_SECONDS
that triggersminer_sync_simple.rb
followed 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.rs
causes network traffic, and invalidates the analytics. This is time consuming.Extend the
config.toml
with 2 parameters:miner_sync_interval=24h
andanalytics_interval=1h
.This can help finding a sweet spot.
The text was updated successfully, but these errors were encountered: