This repository has been archived by the owner on Mar 20, 2021. It is now read-only.
Architecture
OtterTune is comprised of two components:(1) client-side controller and (2) server-side tuning manager
The controller connects to the target DBMS, collects its knob/metric data, transforms the collected information into the universal JSON schema. The tuning manager stores the information in the data repository and schedules a new task with the job scheduler to compute the next configuration for the target DBMS to try. The driver (1) sends the information to the tuning manager, (2) gets a token from the tuning manager, (3) uses this token to check status of the tuning job, and (4) gets the recommended configuration when the job finishes. The driver then installs the new configuration and restarts the target DBMS.