DoiT is a global technology company that provides intelligent software and unrivaled multicloud expertise to digital native organizations.
With nearly 2,500 years of cumulative cloud operations experience, DoiT works alongside more than 3,000 customers in 70+ countries to save them time and money.
Our migration has been straight forward. The BLUE/GREEN method should work well on AWS. MySQLshell tools for migration really helped to confirm any issues. Development > Staging > Production.
Hi. Currently we have workloads only in the morning time from say 4 am to 12 noon. And we are paying 35k for bq. Do you think we can move to flat pricing to save cost. The max slot we use is about 2000 during the peak time
As of July 5th 2023, you can't switch a project to be on flat-rate pricing, so your options for BigQuery are either on-demand or Editions. Some follow-up questions to help us make a recommendation: Are you consistently using 2000 slots during 4am - 12 noon, or is it very spiky? If spiky, are the spikes at the same times during that timeframe? Additionally, how many TiB of data is being processed per day during that timeframe? Last question, are you using anything like Looker or dbt? If so, there could be some tricks you could do to bring your slot consumption down from 2000.
Interesting content, thank you! Couple of times I had performance issues with Aurora Mysql. I tried increasing the class of the db instance, I also tried adding read replica but it didnt help at all - the app was running long queries without parallelism and it was only using one core of the RDS so the more powerful instance did not change the times at all. For that case (and another similar one) switching to RDS MariaDB worked out. It turned to be 2-3 times faster than Aurora Mysql with same instance class. Could you comment?
Thanks for watching the episode + glad to hear you liked the content :). Now to answer your question (via Kate from the episode): "MySQL is in general a single-threaded database designed for high volumes of queries as opposed to large analytic or data warehouse type queries. MariaDB and MySQL are optimized for different types of workloads. Something that works well in one may not work well in the other. MySQL tends to excel at complex joins and sub-queries whereas MariaDB is often better at recursive CTEs and analytics. If you wished to stay using MySQL rather than MariaDB, then you can look at parallel query on RDS Aurora MySQL. This allows you to run complex queries directly against the storage layer in a parallel fashion. docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/aurora-mysql-parallel-query.html"
Here you go: engineering.doit.com/aws-public-ipv4-price-increase-the-complete-guide-73c4c62ae18e I've also just updated the episode description with it, so thanks for asking!
