|
I would like to design a relatively generic model for a data queue-driven, dynamically scaling subsystem. It would seem obvious that the main part of this is the job that monitors the queue depth or response time and starts or ends additional jobs as needed. But, that's about all I have worked out. Has anyone developed a generic design for such a thing. I'm thinking it would be controlled by parms such as minimum/maximum number of jobs, min delay before additional job started, min depth before additional job started, how often to check...but if someone has already gone through this exercise perhaps they would consider sharing what a flexible set of controlling parameters consists of, and any other gotchas? And is there a shorter term for this sort of thing besides "data queue-driven, dynamically scaling subsystem?" Kind regards, Zak Metz . NOTICE: This E-mail may contain confidential information. If you are not the addressee or the intended recipient please do not read this E-mail and please immediately delete this e-mail message and any attachments from your workstation or network mail system. If you are the addressee or the intended recipient and you save or print a copy of this E-mail, please place it in an appropriate file, depending on whether confidential information is contained in the message.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.