sl_cache (E)​/Texture DB

Texture DB

• A Plain file or Berkeley DB can be used as a Texture DB as of v1.0.0.
• When sl_cache is started with -fdb option, Berkeley DB is used. Default is Plain file.
• Even with the default plain file specified the cache works fast enough.
• If you wish to use the Berkeley DB then you will also need to specify the --enable-db option when running configure prior to building sl_proxy and TUIS_Lib.

Plain File

• A directory named 'cache ' is made as a work directory in Temp_File_Dir, and subdirectories named 00, 01, ......., fe, and ff are made in this directory.
  
• Further subdirectories named 00, 01, ......, fe and ff are then made in each of those subdirectories.
• These correspond to the first and second bytes respectively of the texture data GUID. Texture data are sorted and saved in their corresponding (sub)subdirectories.
• Texture data are save with the file name GUID.# where # is a number.
• The number # is a serial number used for when the texture data is divided into multiple parts. The part numbered 0 contains the header (Jpeg2000) of the file.
• The texture data is saved without change.

Ex.) /var/sl_proxy/cache/f8/f7/f8f7b3af-1f42-​c2ec-0bbd-a3cf0751f837.0

Berkeley DB

• A directory named 'cache ' is made as a working directory in Temp_File_Dir, and subdirectories named 00, 01, ......., fe, and ff are made in this directory.
  
• Texture data are sorted by the first hexadecimal number (byte) of the texture data GUID. Texture data within these categories are then saved using Berkeley DB. Therefore, only one Berkey DB file is made in each subdirectory named 00, 01, ....., fe, and ff.
• The file name used is sl_cache_XX.db where XX is the first byte of the GUID.
• Texture data is saved without change.

Ex.) /var/sl_proxy/cache/f8/sl_cache_f8.db

MySQL

• Not yet supported.