- 최신
- 최다 투표
- 가장 많은 댓글
To improve the performance of your queries, I recommend first checking the execution plan and wait events during execution. RDS Performance Insights can provide insight into wait types. You can also reference the documentation below for troubleshooting guidance.
While the RDS OS is optimized, it still requires some resources. A T2.Micro instance has only 1 vCPU and 1GB of memory. After evaluating the current SQL Server metrics, you may want to consider upsizing the instance if more compute or memory resources are needed.
Blogs for reference: Troubleshoot slow-running queries in SQL Server: https://learn.microsoft.com/en-us/troubleshoot/sql/database-engine/performance/troubleshoot-slow-running-queries
Performance Insights metrics for DB instances: https://docs.aws.amazon.com/prescriptive-guidance/latest/amazon-rds-monitoring-alerting/db-instance-performance-insights.html
Best practices for configuring performance parameters for Amazon RDS for SQL Server: https://aws.amazon.com/blogs/database/best-practices-for-configuring-performance-parameters-for-amazon-rds-for-sql-server/
Question: Is there any possibility that AWS could set on 25sec the default value for response-time after some request rate on Data Base server? My question is based on all the tests that I've been performed over my server where I've received that response time on each query, I don't understand why is not changing it's always 25sec.
관련 콘텐츠
AWS 공식업데이트됨 일 년 전- AWS 공식업데이트됨 2년 전
I'll check those docs, thanks a lot for your support. Anyway I would let you know that my DataBase server isn't always running slow. The same query which takes 25sec to response sometimes takes 0sec to give me the result. Seeing AWS metrics I can see that 7 connections and 30% CPU utilization are enough to get that 25sec delay, and it's really weird to see a server being affected by those values.