That's why you don't use AWS 'auto' scaling. Every application has it's sweet spot and it's simpler to roll your own when you know best.
When AWS Autoscale Doesn’t
91–99 of 99 posts
Re: When AWS Autoscale Doesn’t
#92Earlier quoted context omitted.
While the poster was aware of it, he did not provide a solution whereas DVassallo provided a valuable step by step on how to do it properly. Which may help others in the future. Think long and hard why you felt it necessary to make your comment and what value it actually provided.
> Think long and hard why you felt it necessary to make your comment and what value it actually provided. Yeah, that's what I was telling the other poster in a nicer way. Same goes to you. You can provide advice without repeating criticism for no reason when the person specifically said they did something wrong. And save me the lecturing on "long and hard." My comment has 15 upvotes, so it's pretty unlikely I'm the o…
> You can provide advice without repeating criticism for no reason when the person specifically said they did something wrong.
That statement is a joke, here it is reworded:
> A person should be invulnerable to criticism as long as they make a humbling remark.
Doesn't sound so great now does it.
Also, I'm not surprised you got 15 upvotes. This place has ceased to be a hacker forum for many years now. Too many eternal politically correct Septembers.
Re: When AWS Autoscale Doesn’t
#93Earlier quoted context omitted.
> Think long and hard why you felt it necessary to make your comment and what value it actually provided. Yeah, that's what I was telling the other poster in a nicer way. Same goes to you. You can provide advice without repeating criticism for no reason when the person specifically said they did something wrong. And save me the lecturing on "long and hard." My comment has 15 upvotes, so it's pretty unlikely I'm the o…
> You can provide advice without repeating criticism for no reason when the person specifically said they did something wrong. That statement is a joke, here it is reworded: > A person should be invulnerable to criticism as long as they make a humbling remark. Doesn't sound so great now does it. Also, I'm not surprised you got 15 upvotes. This place has ceased to be a hacker forum for many years now. Too many eternal…
A strawman argument + when your view is not popular, the environment must be the problem. Classic undefeatable argument. I'm surprised you have problems getting along here.
Re: When AWS Autoscale Doesn’t
#94Earlier quoted context omitted.
Hi, Jelastic founder is here. Thank you for mentioning our product. Vertical scaling is not a marketing :), it's reality. Jelastic public cloud providers offer automatic vertical scaling with pay-as-you-use billing model (please do not confuse with pay-as-you-go). Except this our team helps related technologies to become more elastic, for example Java https://jelastic.com/blog/elastic-jvm-vertical-scaling/ Regarding…
Regarding 1: Any easy set up guide for native mode? Regarding 2: Is there any fundamental reason why full compatibility will never work?
1 - An easy way is go to marketplace and print Docker in the search field, choose Engine or Swarm, press install. There is one more article that will be helpful https://jelastic.com/blog/docker-engine-auto-install-connect...
2 - As Docker, Open Containers and other related technologies evolve the difference between system and application containers gets slimmer over the time. As an example well known issue with memory limits https://jelastic.com/blog/java-and-memory-limits-in-containe... now can be solved with help of lxcfs https://medium.com/@Alibaba_Cloud/kubernetes-demystified-usi.... I hope at some point we will be able to use benefits of both in one container engine.
Re: When AWS Autoscale Doesn’t
#95Earlier quoted context omitted.
> You can provide advice without repeating criticism for no reason when the person specifically said they did something wrong. That statement is a joke, here it is reworded: > A person should be invulnerable to criticism as long as they make a humbling remark. Doesn't sound so great now does it. Also, I'm not surprised you got 15 upvotes. This place has ceased to be a hacker forum for many years now. Too many eternal…
A strawman argument + when your view is not popular, the environment must be the problem. Classic undefeatable argument. I'm surprised you have problems getting along here.
> when your view is not popular, the environment must be the problem
You were the one using upvotes to validate your argument when it's a fact that posting a political opinion in either a left and right forum will net highly different responses. Of course the environment plays a part.
Won't even bother dissecting the first shot. Your arguments have been weak at best till now this final one was the final straw, man.
Re: When AWS Autoscale Doesn’t
#96Earlier quoted context omitted.
While the poster was aware of it, he did not provide a solution whereas DVassallo provided a valuable step by step on how to do it properly. Which may help others in the future. Think long and hard why you felt it necessary to make your comment and what value it actually provided.
If this is still a pitfall for users of AWS ~5 years in.. then its not a fault of my communication... You know what I think its a fault of: Lack of a canonical DevOps "university" stemmed from SV startups. DevOps at this point should not just be a degree -- it should be a freaking field of study and classes offered by YC.... Look at their pedigree of companies at scale. We should all make an effort to give back in th…
devops as a field of serious study is pretty pathetic.
I wouldn't trust a devops 'grad' to do anything or
know anything.
But with the resurgence in certs and boot camps and
other snake oil making $$ why not?
Re: When AWS Autoscale Doesn’t
#97Earlier quoted context omitted.
Batching incoming requests, for one. Kinesis only allows 5 write requests per second per shard, for example. As well, Lambda have limits regarding concurrent executions and are very slow (10s) if needing VPC connectivity (in this case the default concurrent lambda limit is 350 due to ENIs)
Hmm... I don't see anything in the docs implying that - Kinesis API docs say it's possible to ingest 1000 records or 1MB per shard per second. There's a 5/s limit on reads however but those deal with batches of records anyway. We have one service running that consumes data to a Kinesis stream published as an API GW endpoint. Preprocessing is done in Lambda in batches of 100 records and the processed records get pushe…
Yes, sorry, i confused it with GetRercords limit.
Re: When AWS Autoscale Doesn’t
#98Earlier quoted context omitted.
Batching incoming requests, for one. Kinesis only allows 5 write requests per second per shard, for example. As well, Lambda have limits regarding concurrent executions and are very slow (10s) if needing VPC connectivity (in this case the default concurrent lambda limit is 350 due to ENIs)
I suppose you could just ask them to raise the limits?
[deleted]
Re: When AWS Autoscale Doesn’t
#99Having used ECS quite a bit, I do not recommend anyone building a new stack based on it. Kubernetes solves everything ECS solves, but usually better and without sveral of the issues mentioned here. Last time I checked, AWS was still lagging behind Azure and GCP on Kubernetes, but I have a strong feeling they're prioritizing improving EKS over ECS. If you're already invested in ECS it's a different story, of course.
We use a ton of ECS, for running batch processing for our data pipeline, 4ish small internal webapps/microservices, and our Jenkins testing compute. Some of the problems we're seeing is task placement and waiting is too hard (we had to write our own jittered waiter to not overload the ecs api endpoints when asking if our tasks are ready to place). Scaling the underlining EC2 instances is slow. The task definition=>fa…
> Scaling the underlining EC2 instances is slow.
Do you mind if I ask how long this takes right now with you and how long you expect it to take to be fast?