New Database Migration - Pricing -> Mysql
Hi everyone!
I've been reading about the plan for migration/migrate the databases we are using....
I have a question. for example, I have been paying like $25/$30 for my services and most of the cost is on the database side. 70/80% of the total cost.
Does the migration attempts to improve this type of scenario?
Any suggestion or any common scenario I'm facing with?
I'm using Mysql db
Perhaps one SQL database is better handled than another? in terms of cost/performance?
9 Replies
Project ID:
f4ffaf00-bf8e-4fc7-8e95-9d64d9995b8df4ffaf00-bf8e-4fc7-8e95-9d64d9995b8d
mysql is known to use a lot of memory, in fact it will use about 500mb on a fresh deploy, so it using ~1gb is not out of the ordinary at all
the new mysql databases do use a newer version of mysql but thats unlikely to be any more memory efficient
my recommendation would be to look into mariadb, it should be a drop in replacement and could use less memory
(id recommend my template if youd like to deploy mariadb)
Awesome!! I'll talk with the Team!
thank you very much Brody!
no problem!
Sorry to jump in this thread as it seems very interesting; regarding RAM usage, which one do you think is best, Brody? I guess it depends very much on the use case, but wasn't Mariadb built using a MySQL layer? How big is the ram drop between the two databases new fresh?
these arent fresh but i have never put any data into them, this also isnt an accurate representation of the ratio between the two when used by an actual app
yeah, I know it isn't trustable data..., but it just seems interesting the difference between them... thanks for the screenshot
no problem!