At work with Aurora MySQL I believed would be a draft, but its delicate variances make me scratch my head. Thus, I want to find out further about this and transcribe a post.
What is Aurora?
It's a mySQL wire procedure well-suited storage organization system that sits on top of mySQL and adjusts some innodb internals. You can read approximately more of the architecture here: I contemplate of it as a Proxy Storing Engine System
The changes start from fair starting the server. Aurora MySQL has Enormous Page provision turned on by defaulting since AWS introductions Aurora MySQL server with their tradition flag for innodb big page provision:
innodb_shared_buffer_pool_uses_huge_pages
This is not an open source situation known by MySQL authorized build. In fact, there is not much info on this situation at all. I can only accept RDS instances are organized with Huge page provision as comprehensive here and this custom situation for Aurora goes big page provision on for mysqld.
So, what else is dissimilar between Aurora and Innodb? From Amazon's documents
The following MySQL limitations do not put on to Aurora MySQL:
innodb_adaptive_flushing
innodb_adaptive_flushing_lwm
innodb_checksum_algorithm
innodb_doublewrite
innodb_flush_method
innodb_flush_neighbors
innodb_io_capacity
innodb_io_capacity_max
innodb_log_buffer_size
innodb_log_file_size
innodb_log_files_in_group
innodb_max_dirty_pages_pct
innodb_use_native_aio
innodb_write_io_threads
thread_cache_size
The subsequent MySQL standing variables do not put on to Aurora MySQL:
innodb_buffer_pool_bytes_dirty
innodb_buffer_pool_pages_dirty
innodb_buffer_pool_pages_flushed
Note
These leans are not comprehensive.
In immediate, Aurora uses mySQL but it's also a deposit on top of mySQL. In all core, it's just additional storage engine which splits Innodb and delivers administration primitives made into the DBMS system.
Comments