Is there any standard for scaling code repositorie...
# ask-community
a
Is there any standard for scaling code repositories in k8s? I have a job that starts other jobs with graphql, maybe queuing 200 job runs (i have a concurrency limit of 2 jobs running), and when queuing up jobs I got a graphql timeout error of 60 seconds. Is that due to the performance of the code repository?
a
do you have the stack trace for the exact error you got?
Is there any standard for scaling code repositories in k8s?
one data point is what resources we give our serverless customers in dagster cloud, communicated here as “Sensors receive” as schedule and sensor evaluation happen on the code server