mySQL droplet size

I am looking to start a small project and looking into reading data from mutiple sources and inserting the data into a sql database. I plan to run my script every hour to start and it will add about 500~ records which each have about 10 fields. On a daily there will be about 12,000 records inserted into the database.

I currently have a $10 droplet. Do you think this will be sufficate for my requirements and how far down the line do you think I will need to upgrade to handle more data?

Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

hello thanks for sharing thsi wonderfull information with us .


Hi @jimmytu

It all depends. I have a project, where there’s currently about 2 million records across 17 tables with 124 columns. Most columns are bigint and varchar, but there are a few text. There is roughly 1,000 new records every day. All columns are indexed, so there are no “joins without index” and there’s no cache in the system, so everything is “real time”. The system does about 1 million queries per day, where 98% is read and 2% is write.

This is being hosted on a single $10. My current estimate is that I can get to 4-5 million records before I need more RAM to avoid swapping.

Without knowing the exact data structure and how everything is tuned, then it’s difficult to know the precise resource demands of your project. I did a test a few months ago, where I just created a droplet with changing any configuration (meaning no tuning done at all) and removed all the indexes from the database (besides Primary Key). This resulted in me having to scale the droplet to $80, but it was still slower than the properly configured and tuned $10 droplet. At $160 it was a bit faster.