4 ms·
The growth rate of a queue is not constant, it could get bigger during the day, but smaller at night, since customers are not using the service.
by vhcr 4y ago
The growth rate of a queue is not constant, it could get bigger during the day, but smaller at night, since customers are not using the service.
- roflyear 4y agoIf you're just making people wait 12 hours, or five minutes, or whatever - you aren't saving on compute. You're just adding a buffer. Maybe that is what you want, but it should be intentional.
- happymellon 4y agoThis is usually the approach of people with fixed compute. If I have a VPS then I'll let it churn through the backlog overnight. But this is also where the disagreement comes in with flexible serverless workers. They generally do not cost more, so you'll end up spending $24 in an hour rather than $1 an hour all day. If the serverless costs more then you are likely not working through your backlog. I agree it should be a business decision, so you catch up on weekends instead for example, but non-technical folks don't always grasp those numbers and that they are getting a lag with their data.
- roflyear 4y agoIt is a little counterintuitive, but "churn through overnight" still means you're decreasing the queue size. You're right that the cost really ends up being roughly the same, unless your service gives you a discount for compute overnight or something.
- happymellon 4y agoCompletely agree that the queue still goes down, I just see comments on here about folks preferring a VPS because they run it 24/7 for the same price. That is probably fine for their scenario but the non-technical members probably don't understand that they aren't saving money by doing it this method but are adding a delay. That is my only point.
- roflyear 4y agoExactly. I think a lot of people in this thread don't understand they "aren't saving money by doing it this method but are adding a delay" with their complicated auto scaling worker setup lol