How can I improve Microsoft Azure performance without guessing?
A performance change should improve the measured workload without sacrificing correctness or wasting capacity. Which measurements and bottlenecks should be considered first?
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
A performance change should improve the measured workload without sacrificing correctness or wasting capacity. Which measurements and bottlenecks should be considered first?
I'm looking for a way to export a yaml file from a deployed component but without the cluster specific information. kubectl get MYOBJECT --export -o yaml > my.yaml but since "export" is now deprecated (since 1.14 and should normally disappear in 1.18 (didn't find it in changelog), what would be an alternative ? thanks
We have a EKS setup provisioned where we use a Cloud Native Buildpacks based Tekton Pipeline our PipelineRuns are stuck and pending forever without getting a Pod resource. We created a PersistentVolumeClaim like this: apiVersion: v1 kind: PersistentVolumeClaim metadata: name: buildpacks-source-pvc spec: accessModes: - ReadWriteOnce resources: requests: stora
I'm trying to use Federated Authentication to enable login with Microsoft AD. It works fine and we can login. But when I call LOGOUT endpoint as the documentation says ( https://docs.aws.amazon.com/cognito/latest/developerguide/logout-endpoint.html ) and try to login again I'm not being redirected to Microsoft page to type my email and password again. It see
I´m trying to publish the html code from one cloud source repository to a public storage bucket in gcp through a cloud build trigger . However , I get the following error in the build each time I push to the master branch. generic::invalid_argument: generic::invalid_argument: if 'build.service_account' is specified, the build must either (a) specify 'build.l
What is the difference between a timeout and an HTTP 500 response? This Q&A focuses on interpreting the evidence before changing application or network settings.
We run a single Notion integration token across several workspaces, and under concurrent sync jobs we see intermittent failures that look like throttling. Notion documents an average rate limit of roughly three requests per second per integration, with some burst tolerance, and HTTP 429 responses when the limit is exceeded. The uncertainty is how that budget
Before optimizing an Elasticsearch cluster, I need to confirm where the indexing bottleneck resides. I plan to query the nodes stats API for metrics such as indexing_pressure, thread_pool queue sizes, and merge throttling times, while also sampling hot threads to see CPU contention. However, I am unsure which combination of these metrics most reliably indica
I am looking to make use of the native import/export that comes with ES6. I am using Serverless Containers within AWS Lambda. I have my Dockerfile which looks like this: FROM public.ecr.aws/lambda/nodejs:14 COPY app ./ RUN npm install CMD [ "app.handler" ] I then have an app directory with my application code. The app.js code looks like this: import { succes