Tweet
Other possible load reduction techniques include assigning each license server client (as in client to your servers) a discreet time of day for contacting your servers each day (week, etc.)
You keep a database and round robin out these times to all the users' license servers so that no more than 1/2880 of users contact your server at one time. (2880 is the number of 30 sec intervals you have to work with per day). This is if you assigned each user a spot every :30sec. So when people borrow a license you query your database of times already allocated (N+ 30 sec) and select the slot least used and assign it to that license server. Or break it down into 15 sec intervals, even... I doubt it takes that long to process a request for a few nodes. You could break it into 5 sec chunks. The user's local license server only re-borrows at the prescribed time. Sure clocks vary, but you will end up with a much more even load, FAR more even than 40 render nodes hitting your servers at once for those who have not borrowed their licenses.
The goal is to take the auto-renewal load and spread it out so it is nothing to worry about. Since this is something you have total control over it should be easy to manage. In theory of course
Again, thanks for listening. I see a lot of effort has put into licensing, and I thank you and your team for that. I am just an ideas guy, and some of those ideas may be crap (a lot of them, I am told), but perhaps one of them makes something go "click" for you or one of your team. Then all my rambling has proved useful... Maybe
Again, than you for listening. This is what sets Chaos apart from a lot of companies these days.
You keep a database and round robin out these times to all the users' license servers so that no more than 1/2880 of users contact your server at one time. (2880 is the number of 30 sec intervals you have to work with per day). This is if you assigned each user a spot every :30sec. So when people borrow a license you query your database of times already allocated (N+ 30 sec) and select the slot least used and assign it to that license server. Or break it down into 15 sec intervals, even... I doubt it takes that long to process a request for a few nodes. You could break it into 5 sec chunks. The user's local license server only re-borrows at the prescribed time. Sure clocks vary, but you will end up with a much more even load, FAR more even than 40 render nodes hitting your servers at once for those who have not borrowed their licenses.
The goal is to take the auto-renewal load and spread it out so it is nothing to worry about. Since this is something you have total control over it should be easy to manage. In theory of course
Again, thanks for listening. I see a lot of effort has put into licensing, and I thank you and your team for that. I am just an ideas guy, and some of those ideas may be crap (a lot of them, I am told), but perhaps one of them makes something go "click" for you or one of your team. Then all my rambling has proved useful... Maybe
Again, than you for listening. This is what sets Chaos apart from a lot of companies these days.
Comment