AudioClip Database

The microservice stores audio clips in a in-memory database. As such, the database does not persist if the microservice is closed or restarted. Moreover this database is not shared between microservices.

The AudioClip database can be parametrized via the configuration file of the microservice.

TTL

The AudioClip database supports a TTL option (clip_db_ttl) which specifies the length (in seconds) of the time to live for any given audio clip.

The audio clip last usage is refreshed every time a call to GetAvatarFacePose is made to the corresponding clip.

On upload, a background tasks deletes the clips which the last used date is older than the TTL option. This means that while no more audio clips are uploaded, the service does not invalidate any clip.

Maximum size

It is possible to set a maximum size to the audio clip database (in bytes) using the clip_db_max_size option. This will ensure that the service clip database never grows beyond this clip size. Note that the size is calculated on upload, after applying the TTL purges regarding old audio clips.