Skip to content Skip to main navigation Skip to footer

Understand SPE configuration

Database settings

SQLite is a great database for most evaluation use cases. However if you would like to use the database as the logging target, it must be switched to MySQL type of database. Also, if your architecture requires shared user resources, you have to use the MySQL type of database. Supported MySQL engines are based on original MySQL v5.6+ or MariaDBv10+.

# Type of database
# Suported are SQLite and MySql
server.db.engine = SQLite

The database is mainly used as the working cache – details about SPE user accounts are saved in the database as permanent objects, speech processing results are stored inside as dependent objects: the results are available as long as the audio recording is present in the home directory; whenever audio files are deleted from the storage using the appropriate RESTful API call, all related results are erased from database.

# Store results of technologies in database
server.db.save_results = true<
# Set SQLite database file
server.db.sqlite.data_source = ${application.dir}phxspe.sqlite

When you decide for more advanced database usage, configure the connector using these directives:

# MySql database configuration
# server.db.engine = MySql
# Database address
# =
# Database port
# server.db.mysql.port = 3306
# Name of database
# server.db.mysql.db = phxspe
# Database user name
# server.db.mysql.user = phonexia
# Database password
# server.db.mysql.password = phonexia
# Database options
# server.db.mysql.options = compress=true;auto-reconnect=true
# Maximum of MySQL database connections at the time. Default is 32
# server.db.mysql.max_connections = 32
# Maximum size of in-memory cache for calibrated voice-prints of speaker models. Default is 100
# server.db.sid_model_calib_vp_cache_size = 100