Channels
ask-ai
dagster-de
topic-async-execution
dagster-jp
dagster-cube
gigs-freelance
dagster-wandb
dagster-feedback
dagster-machine-learning
dagster-bigquery
dagster-university
dagster-support
dagster-dask
dagster-snowflake
dagster-releases
dagster-dbt
faq-read-me-before-posting
tools
dagster-insights
dagster-pipes
project-flexible-range-backfills
data-platform-design
events
dagster-serverless
dagster-noteable
introductions
dagster-airflow
dagster-cloud
random
dagster-airbyte
dagster-spatial
announcements
github-discussions
豆瓣酱帮
dagstereo
dagster-ecs
dagster-kubernetes
jobs
dagster-showcase
data-quality-asset-checks
Powered by
#dagster-support
Title
# dagster-support
t
tamolo
08/08/2022, 3:56 AM
Hi foks, is there any reason why we limit run_status_sensor to just 5 records each time
https://github.com/dagster-io/dagster/blob/master/python_modules/dagster/dagster/_core/definitions/run_status_sensor_definition.py#L351-L365
. With this limit even when we set minimum_interval_seconds=1, the maximum metrics we can collect is 5 metrics per second. If we have 10 metrics for a seconds then the metrics will be delayed before actually collected
c
claire
08/08/2022, 9:08 PM
Hi
@tamolo
. No strong reason why this limit was set. How many metrics do you intend to collect per second? We could try to increase the limit, though it could potentially slow down the query.
3 Views
Post