![]() A simple group by query: select ColA, count(*) group by ColA took about 2. Results: The AWS Postgres instance had an advantage in latency because it was hosted in the same physical datacenter as the app (AWS us-west-1 which is San.The table has a state column that is very often one of the first filters users use as often users only want to see one or a set of particular states. So there might be other ways to optimize performance without upgrading the instance? For example, it might be possible that partitioning would be helpful. Again, not sure if upgrading the instance would help with that? I should also note that I have no added primary keys or indices. Compare price, features, and reviews of the software side-by-side to make the best choice for your business. A select count(*) from that table took about 15 minutes (in the first run in the second run it took about 3 minutes, probably because it's caching statistics? 3 minutes still seems slow to me.).Would upgrading the instance help with that? If so, I'm not sure what I would want to upgrade to? I just tested one right now, creating a table, and loading the CSV into the table (using \copy) of a 11 GB file (35,401,551 rows and 40 columns) took about 27 minutes. Loading a table from CSVs: We have a lot of CSVs sitting on disk that I'll be loading into the PostgreSQL database.Our team is also very budget conscious right now so I'm trying to scope this out before advocating to upgrade. However, it's hard for me to understand how this compares to other instances. I started with the Free Tier for now db.t2.micro just to gain some experience, develop, and test out what I need. There are a few other tables that are around 10 GB. The largest table will be about 80GB and will be queried frequently. However, there are a few tables that are quite large. The database will contain about 300 - 500 GB of data.Our use case is primarily for analytics/data science purposes there will be no live applications running on top of it. I'll likely be turning the database on during normal business hours and off afterwards. We're primarily a small team (less than 5 users) of data analysts/data scientists. ![]() I'm trying to figure out what are the practical differences between Amazon RDS Instance Types. Amazon still handles all the fiddly work of managing the databasebut under the hood, it’s quite different. It’s API-compatible with MySQL and PostgreSQL, and it’s meant to be a drop-in replacement. Externally, it behaves like any other RDS database. I'm relatively new to setting up PostgreSQL databases in general and AWS. Amazon created Aurora to be a cloud-first database.
0 Comments
Leave a Reply. |