Disk or Database Bottleneck

Danka sir. I was getting to that same conclusion when I looked at these last night but wasn’t sure if that was the only thing showing as an issue. But yeah a lot of AstDB delays in the backtraces.

1 Like

not sure on the type of file system, but you can try some disk mount options to see if they help,

ie noatime,

Some additional info How to Check Disk Queue Length in Linux

1 Like

Can you clarify storage issues? Is there a way to see which AMI user issued the database show command?

Below is the systat, that @dicko recommended, that covers the time period of the backtrace.

From the backtrace no. The sqlite3 database is stored on disk, with the kernel (and maybe the sqlite3 library) caching some things in memory. If it has to go to disk, and I/O is slow, then the database operations will be slow, which will cause users of the database to take longer, which can then cascade to causing other things to wait for access to the database.

Is there a way to see that? Would I see disk issues on the systat? It was pretty much happening all day yesterday. Thanks for your thoughts here, very helpful.

I haven’t used it, so I can’t answer that. I’m just speaking from past experience. I’ve used iostat in the past to diagnose I/O, which I see is in there I think so lemme look more…

Sorry, it was ioping that I used against the specific storage device.

Thanks, havent used systat before this, but from what I think I am seeing, I dont see what I would think is an IO bottleneck. could be wrong though.

The worst is see is
03:00:01 PM dev8-32 28.82 0.85 25413.87 881.77 1.32 45.63 0.36 1.03
03:00:01 PM dev253-0 50.41 304.96 25985.63 521.59 1.34 26.66 0.32 1.59

which the disk queue length is over 1. But this is not bad yet. Over 3 or 4 would be more concerning.

1 Like

We found the AMI account running this command. It had a 10000 timeout vs the usual 100 we see on our other accounts. They have disabled the script it was running for now, and will look for alternative/better optimization. So far (2 days) the issues have subsided too.

Was it a custom AMI application?

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.