Skip to content

Conversation

@spacejam
Copy link
Contributor

No description provided.

Copy link

@ghost ghost left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@ghost ghost merged commit 8c647cf into master Aug 15, 2019
@spacejam spacejam deleted the tyler_randomized_spindown branch August 16, 2019 10:08
@yoshuawuyts
Copy link
Contributor

yoshuawuyts commented Aug 16, 2019

10 secs spin down sounds a bit on the high end to me, but admittedly my intuition here is mostly theoretical. I'd be keen to talk more about this at a later time to understand it better (:

@spacejam
Copy link
Contributor Author

spacejam commented Aug 21, 2019

@yoshuawuyts This is an autoscaling system. One of the most common mistakes when building such systems is to release processing resources too quickly, repeatedly incurring latency hiccups during spin-up when load bursts.

That said, this would probably be better if it followed a FILO-based threadpool approach, rather than a FIFO which will keep threads alive as long as they receive any work before their timeout, keeping 10k threads open without all that much actually happening. This would let most of the threads time-out when mostly idle.

This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants