Since migrating to Windows Server 2008 Datacenter for our Amazon EC2 instances I have noticed on many occasions that when a new instance is starting up RAC agent will cause the CPU to spike up to 100% for a good half an hour, at times the CPU spike never comes down and effectively renders the instance unusable..
After some digging around, I found this article which tells you how to disable the RAC agent:
In case the link stops working in the future, here’s the 4 steps you need to do:
1. go to Control Panel –> Administrative Tools –> Computer Management
2. navigate to System Tools –> Task Scheduler –> Task Scheduler Library –> Microsoft –> Windows –> RAC
3. right click RAC, select View –> Show Hidden Tasks
4. right click on the displayed task, and select Disable
I specialise in rapidly transitioning teams to serverless and building production-ready services on AWS.
Are you struggling with serverless or need guidance on best practices? Do you want someone to review your architecture and help you avoid costly mistakes down the line? Whatever the case, I’m here to help.
Check out my new course, Complete Guide to AWS Step Functions. In this course, we’ll cover everything you need to know to use AWS Step Functions service effectively. Including basic concepts, HTTP and event triggers, activities, callbacks, nested workflows, design patterns and best practices.
Here is a complete list of all my posts on serverless and AWS Lambda. In the meantime, here are a few of my most popular blog posts.
- Lambda optimization tip – enable HTTP keep-alive
- You are thinking about serverless costs all wrong
- Many faced threats to Serverless security
- We can do better than percentile latencies
- I’m afraid you’re thinking about AWS Lambda cold starts all wrong
- Yubl’s road to Serverless
- AWS Lambda – should you have few monolithic functions or many single-purposed functions?
- AWS Lambda – compare coldstart time with different languages, memory and code sizes
- Guys, we’re doing pagination wrong