Skip to content
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.

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

Any examples for using node-usage for load-balancing? #9

Open
smeijer opened this issue Feb 6, 2015 · 1 comment
Open

Any examples for using node-usage for load-balancing? #9

smeijer opened this issue Feb 6, 2015 · 1 comment

Comments

@smeijer
Copy link

smeijer commented Feb 6, 2015

Thank you for this great meteor package! I also noticed your great (a bit older) node library node-usage.

So, is there any way of integrating these two? In the way that the system-resources are being taken into account for the balancing logic? I think that would be the ultimate goal, pointing the visitor to the most idle server, and ultimately alerting some system administrators when all servers become to heavily loaded (so he can spawn a new server).

@arunoda
Copy link
Member

arunoda commented Feb 6, 2015

Yes that is. We might do something similar with integrating kadira. So, we
can use more resources.
We've not planned yet, but it'll be there for sure.

On Fri Feb 06 2015 at 4:35:45 PM smeijer [email protected] wrote:

Thank you for this great meteor package! I also noticed your great (a bit
older) node library node-usage https://github.com/arunoda/node-usage.

So, is there any way of integrating these two? In the way that the
system-resources are being taken into account for the balancing logic? I
think that would be the ultimate goal, pointing the visitor to the most
idle server, and ultimately alerting some system administrators when all
servers become to heavily loaded (so he can spawn a new server).


Reply to this email directly or view it on GitHub
#9.

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

No branches or pull requests

2 participants