3 ms·

> People who live in the real world and have to do real work need to use real world tools, and one of which is AWS Lambda. Another real tool is dedicated serve

> People who live in the real world and have to do real work need to use real world tools, and one of which is AWS Lambda. Another real tool is dedicated servers, something people used before "cloud" and something that people who care about performance still uses. AWS even offers dedicated servers themselves, so not sure why you would need to involve any "boutique service provider". Otherwise you have OVH, Hetzner and a range of others who compete well with AWS on dedicated instances as well, neither I'd say are "boutique". > rewrite a whole application stack from scratch in your pet performant language Not sure where this comes from, which one of these languages are "pet performant (SIC) languages"? > who in their right mind would get accountants involved in a goal to shave a few milliseconds over a few gRPC calls Hmm, unless the accountants are involved somehow in the API design (not sure what you're building), I don't know what the accountants have to do with anything here. In the end, AWS and Lambda absolutely does not fit every use case. Depending on your use case, and if it's important a few ms here and there, you chose different solutions. Since this benchmark is about throughoutput, I thought we were discussing the use case of needing the best throughoutput, otherwise this is all off-topic. And with that, I'm just sharing that if that is your focus, you would probably not be using Lambda in the first place, as you'll get very shitty throughoutput and you have to pay a lot, compared to other mature solutions for this that we already had for many many years.

Hikikomori 6y ago
Most instances on AWS get dedicated cpu and memory resources, so noisy neighbors isn't a problem. The difference with metal is that you get the whole box for yourself.
- capableweb 6y ago
  > Most instances on AWS get dedicated cpu and memory resources, so noisy neighbors isn't a problem First time I heard of that and also doesn't match my own experience using AWS. AWS tends to have a lot of noise from neighbors but might be because of the region I was using. Could you link the official statement you got this from? > The difference with metal is that you get the whole box for yourself. Yes, + you normally avoid virtualization as that can have impact on your performance too. I'm glad we agree there is a difference that is worth mentioning when it comes to performance :)
  - Hikikomori 6y ago
    https://youtu.be/mZy6E2I5Rek https://youtu.be/mZy6E2I5Rek At 15 minutes. Afaik it's all but T type instances that get reserved resources. Might have been different in early AWS, pre nitro etc. Something that i just remembered is that in AWS dedicated means that the hardware is dedicated to you, so no other customer vm on it, but you can have multiple vm's on it.
spacemanmatt 6y ago
If you have a large number of users, accounting is involved in virtually everything you do in the capacity of serving them. Engineering history is littered with projects to shave milliseconds or cents off a very small component which is used extremely frequently.
- capableweb 6y ago
  > If you have a large number of users, accounting is involved in virtually everything you do in the capacity of serving them What do you count as "large number of users"? Worked on projects with millions of users, thousands of requests per second and when we refactored based on increasing throughoutput/decreasing latency we had exactly 0 accountants involved, even if the company had accountants in-house and full-time. I think it depends more on the company size than the number of users you have. > Engineering history is littered with projects to shave milliseconds or cents off a very small component which is used extremely frequently. Yup, agree and been there myself, hence my comments about staying away from Lambda and VPS for this kind of focus and go for dedicated instances where this matter.
  - spacemanmatt 6y ago
    > Worked on projects with millions of users Maybe interacting with the finance department was above your pay grade. The bigger the operation, the more costs matter. That's a thumb-rule you can find anywhere.
    - capableweb 6y ago
      > Maybe interacting with the finance department was above your pay grade. It was not, we were a nimble and lightweight team with everyone doing everything they could possibly do. I had insight into accounting and helped them with implementing some stuff and some of the designers helped with frontend as some of them knew HTML and CSS and so on. > The bigger the operation, the more costs matter. That's a thumb-rule you can find anywhere. Yeah... I think I agree? "The bigger the operation" is referring to the employees working for the company, not the number of users right? If so, that was exactly my point. It's about the number of employees that dictate if accountants gets involved or not, not the number of users.

Hikikomori 6y ago

Most instances on AWS get dedicated cpu and memory resources, so noisy neighbors isn't a problem. The difference with metal is that you get the whole box for yourself.

capableweb 6y ago
> Most instances on AWS get dedicated cpu and memory resources, so noisy neighbors isn't a problem First time I heard of that and also doesn't match my own experience using AWS. AWS tends to have a lot of noise from neighbors but might be because of the region I was using. Could you link the official statement you got this from? > The difference with metal is that you get the whole box for yourself. Yes, + you normally avoid virtualization as that can have impact on your performance too. I'm glad we agree there is a difference that is worth mentioning when it comes to performance :)
- Hikikomori 6y ago
  https://youtu.be/mZy6E2I5Rek https://youtu.be/mZy6E2I5Rek At 15 minutes. Afaik it's all but T type instances that get reserved resources. Might have been different in early AWS, pre nitro etc. Something that i just remembered is that in AWS dedicated means that the hardware is dedicated to you, so no other customer vm on it, but you can have multiple vm's on it.

spacemanmatt 6y ago

If you have a large number of users, accounting is involved in virtually everything you do in the capacity of serving them. Engineering history is littered with projects to shave milliseconds or cents off a very small component which is used extremely frequently.

capableweb 6y ago
> If you have a large number of users, accounting is involved in virtually everything you do in the capacity of serving them What do you count as "large number of users"? Worked on projects with millions of users, thousands of requests per second and when we refactored based on increasing throughoutput/decreasing latency we had exactly 0 accountants involved, even if the company had accountants in-house and full-time. I think it depends more on the company size than the number of users you have. > Engineering history is littered with projects to shave milliseconds or cents off a very small component which is used extremely frequently. Yup, agree and been there myself, hence my comments about staying away from Lambda and VPS for this kind of focus and go for dedicated instances where this matter.
- spacemanmatt 6y ago
  > Worked on projects with millions of users Maybe interacting with the finance department was above your pay grade. The bigger the operation, the more costs matter. That's a thumb-rule you can find anywhere.
  - capableweb 6y ago
    > Maybe interacting with the finance department was above your pay grade. It was not, we were a nimble and lightweight team with everyone doing everything they could possibly do. I had insight into accounting and helped them with implementing some stuff and some of the designers helped with frontend as some of them knew HTML and CSS and so on. > The bigger the operation, the more costs matter. That's a thumb-rule you can find anywhere. Yeah... I think I agree? "The bigger the operation" is referring to the employees working for the company, not the number of users right? If so, that was exactly my point. It's about the number of employees that dictate if accountants gets involved or not, not the number of users.