New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

HystrixCommand constructors allocating too much #850

Closed

mattrjacobs opened this issue Aug 6, 2015 · 1 comment

Labels

bug hystrix-core

Contributor

mattrjacobs commented Aug 6, 2015

As outlined in #789, it's an antipattern to allocate a new HystrixCommand.Setter on each HystrixCommand constructor invocation.

mattrjacobs added bug hystrix-core labels

This was referenced Aug 6, 2015

ThreadPoolSize inspected at runtime #789

Closed

Constructor allocation #855

Merged

Contributor Author

mattrjacobs commented Aug 7, 2015

Merged in #855 to address some extra allocation and added documentation of the cached Setter pattern to: https://github.com/Netflix/Hystrix/wiki/How-To-Use#command-name.

mattrjacobs closed this as completed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment