public inbox for [email protected]help / color / mirror / Atom feed
Re: [EXTERNAL] RDS IO Read time 3+ messages / 3 participants [nested] [flat]
* Re: [EXTERNAL] RDS IO Read time @ 2025-03-31 17:54 Eden Aharoni <[email protected]> 0 siblings, 1 reply; 3+ messages in thread From: Eden Aharoni @ 2025-03-31 17:54 UTC (permalink / raw) To: Christophe Pettus <[email protected]>; +Cc: [email protected] <[email protected]> So you believe it's strictly an EBS issue? Get Outlook for Android<https://aka.ms/AAb9ysg; ________________________________ From: Christophe Pettus <[email protected]> Sent: Monday, March 31, 2025 8:43:19 PM To: Eden Aharoni <[email protected]> Cc: [email protected] <[email protected]> Subject: Re: [EXTERNAL] RDS IO Read time [You don't often get email from [email protected]. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ] > On Mar 31, 2025, at 10:32, Eden Aharoni <[email protected]> wrote: > > First, thanks for the reply :) > So, I do know which part is taking a lot of IO time and it's to be honest any node that reads from the disk.. of course, we're running EXPLAIN on our queries (to be more specific we use auto_explain) but we can't seem to find what could cause an index scan that reads 34 MB to take more than a second (1.2 sec).. we do know that our dataset doesn't fit the memory and we were ok with that but with IO being so slow we just don't know what to do anymore. Any other suggestions other than contact AWS (which we did but it seems this path won't lead anywhere). The performance of EBS is definitely a question for AWS. I can say that, in our experience, EBS mounts for RDS almost never approach the stated maximum throughput, although io2 tends to be closer than gp2 or gp3. ^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: [EXTERNAL] RDS IO Read time @ 2025-03-31 18:23 Christophe Pettus <[email protected]> parent: Eden Aharoni <[email protected]> 0 siblings, 1 reply; 3+ messages in thread From: Christophe Pettus @ 2025-03-31 18:23 UTC (permalink / raw) To: Eden Aharoni <[email protected]>; +Cc: [email protected] <[email protected]> > On Mar 31, 2025, at 10:54, Eden Aharoni <[email protected]> wrote: > > So you believe it's strictly an EBS issue? Well, PostgreSQL certainly can read faster than 34MB/s off of disk. With the data you've given, I can't really say if it's purely an EBS issue. ^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: [EXTERNAL] RDS IO Read time @ 2025-03-31 18:33 Adrian Klaver <[email protected]> parent: Christophe Pettus <[email protected]> 0 siblings, 0 replies; 3+ messages in thread From: Adrian Klaver @ 2025-03-31 18:33 UTC (permalink / raw) To: Christophe Pettus <[email protected]>; Eden Aharoni <[email protected]>; +Cc: [email protected] <[email protected]> On 3/31/25 11:23 AM, Christophe Pettus wrote: > > >> On Mar 31, 2025, at 10:54, Eden Aharoni <[email protected]> wrote: >> >> So you believe it's strictly an EBS issue? You are asking about disk I/O, that is the purview of the OS and hardware. In your case both are created and managed by AWS, only they know what is going on behind the scenes. > > Well, PostgreSQL certainly can read faster than 34MB/s off of disk. With the data you've given, I can't really say if it's purely an EBS issue. > -- Adrian Klaver [email protected] ^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~2025-03-31 18:33 UTC | newest] Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2025-03-31 17:54 Re: [EXTERNAL] RDS IO Read time Eden Aharoni <[email protected]> 2025-03-31 18:23 ` Christophe Pettus <[email protected]> 2025-03-31 18:33 ` Adrian Klaver <[email protected]>
This inbox is served by agora; see mirroring instructions for how to clone and mirror all data and code used for this inbox