miketheman

9 ms·

61.
by miketheman 5y ago
I threw together a one-liner to disable: https://twitter.com/mikefiedler/status/1487439545779949571
62.
by miketheman 5y ago
I was very surprised to receive a few emails late on a Friday that a new feature was auto-enabled on AWS accounts that have never run Kubernetes, and informing me that I'll start paying for a service in 30 days unless I disable it.
63.
Amazon GuardDuty Now Protects Amazon Elastic Kubernetes Service Clusters(aws.amazon.com)
1 points by miketheman 5y ago|2 comments
64.
by miketheman 5y ago
Truth! Wouldn't have it any other way. ;)
65.
by miketheman 5y ago
Wow, that's a lot of indirection! I've had the same setup, but only two requests deep. I think that if there's added value of each nginx tier (if each service has static assets, for example), then there may be some benefit, b
66.
by miketheman 5y ago
Possibly! I wasn't trying to get the highest RPS, rather find a baseline and compare per architecture. I also wrote what I knew how write in a short amount of time. ;)
67.
by miketheman 5y ago
I'm not sure I understand? These examples all use the Fargate compute layer and are deployed as a Task which colocates both containers on the same hardware, so there's no cross-machine factors to contend with.
68.
by miketheman 5y ago
Good to know! Would you be interested in performing the same tests and using `wrk` and report the difference?
69.
by miketheman 5y ago
I don't think the `ab` tool does anything special, so it's likely these are closed and reopened after each request. For the purposes of comparison of one architecture to another, this was sufficient, and mimics user behavior well
70.
by miketheman 5y ago
Glad you liked it! In my example, I'm using an unmodified gunicorn runner to load the uvloop worker. So I'm still only using a single worker process. Once I start tweaking the `--workers` count, I get a much higher queries per sec
71.
by miketheman 5y ago
For one, I'm not using `podman`. I'm using Amazon Elastic Container Service (Amazon ECS) on top of the Fargate compute layer, so I don't have to manage much beyond my application.
72.
by miketheman 5y ago
Possibly - however the premise is that I'm running an application on cloud infrastructure that I don't control - which is common today. I tried to call that out in the post.
73.
by miketheman 5y ago
It may, but this is considering the overhead incurred in the local setup - calling the app through a Docker Desktop exposed port. Running locally on macOS produces ~5000 TPS. The `ab` parameters are also not using any sort of concurrency, a
74.
Container-to-Container Communication(miketheman.net)
80 points by miketheman 5y ago|44 comments
75.
by miketheman 5y ago
Above all else, before you get your hackles raised, thank GitHub for giving you as much free services as they do.
76.
A CLI tool to interact with Elgato Lights(github.com)
1 points by miketheman 6y ago|0 comments
77.
Datadog Real User Monitoring(datadoghq.com)
2 points by miketheman 7y ago|0 comments
78.
AWS DeepComposer ️️- personal take so far(miketheman.net)
1 points by miketheman 7y ago|0 comments
79.
TLS Web Tool: Generate Key and CSR(tls.zone)
1 points by miketheman 9y ago|2 comments
80.
Planning for Chaos with MongoDB Atlas: Using the “Test Failover” Button(medium.com)
2 points by miketheman 9y ago|0 comments
81.
Extending ECS Auto-Scaling for Under $2/month with Lambda(miketheman.net)
1 points by miketheman 10y ago|0 comments
82.
The Terraform Book(terraformbook.com)
2 points by miketheman 10y ago|0 comments
83.
by miketheman 10y ago
He fits a caricature of the worst qualities that Americans have come to represent globally. Many dislike this representation, especially in a potential leader.
84.
Datadog's New App Monitoring Product Puts It on Collision Course with New Relic(forbes.com)
2 points by miketheman 10y ago|0 comments
85.
Site Built by Engineer Fans Can Tell When Pokémon GO Servers Are About to Crash(forbes.com)
2 points by miketheman 10y ago|0 comments
86.
Better Together Dating(bettertogetherdating.eu)
4 points by miketheman 10y ago|1 comments
87.
There’s a New Player in Town, Named Habitat(miketheman.net)
1 points by miketheman 10y ago|0 comments
88.
A GitHub Issue in Three Acts for Habitat(github.com)
1 points by miketheman 10y ago|0 comments
89.
by miketheman 10y ago
Thanks for the update. Would the removal of "fucking" allowed the original title to remain? I feel that the title spurred the interest, as evidenced by the amount of discussion. The new title is not nearly as interesting, nor does
90.
by miketheman 10y ago
Someone renamed this. Why?

More ›