Open jaimebrolesi opened 6 years ago
We faced the same issue. You can try to keep the list of tasks small by periodically cleaning up tasks that will never run anymore.
On Fri, May 4, 2018 at 2:58 PM, Jaime Brolesi notifications@github.com wrote:
Guys, I'm scheduling more than 50,000 tasks and the response time for /v1/scheduler/jobs/search?name is extremely slow.
I'm not sure if Chronos was built to handle this amount of tasks, but someone can help me please!?
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/mesos/chronos/issues/873, or mute the thread https://github.com/notifications/unsubscribe-auth/AEfoEKPPEvdhfWfiXpGEKrJlEfENfD1yks5tvM7ugaJpZM4TzUuo .
Guys, I'm scheduling more than 50,000 tasks and the response time for
/v1/scheduler/jobs/search?name
is extremely slow.I'm not sure if Chronos was built to handle this amount of tasks, but someone can help me please!?