Network System Laboratory - Source of sl_cache (E)

View the diff.
Go to sl_cache (E).

* sl_cache [#m18048f6]
[[日本語はこちら>sl_cache]]~

** Outline [#uf52edaf]
-  &font(120%){''&font(Red){Attention};：''}; ''The texture data is downloaded by HTTP(S) since SL Viewer 2.1.1. Therefore, when Viewer since SL Viewer 2.1.1 is used, sl_cache seems to be useless. ''

-''sl_cache'' is a UDP Texture Cache Server for ''[[sl_relay>sl_relay (E)]]'' running on Linux.
-By our measurements, the texture data accounts for about max ''[[80%:http://www.nsl.tuis.ac.jp/xoops/modules/xpwiki/gate.php?way=attach&_noumb&refer=sl_cache&openfile=texture_rate.png]]'' of all UDP data, though it depends on the SIM's status. 
-Cache data is saved in a plain file or Berkeley DB file. (It works fast enough even with a plain file) 
-''sl_cache'' doesn't rewrite the sequence number of UDP packets. It only saves data taking it out of the data stream. 

- ''sl_cache'' is part of ''[[sl_proxy>sl_proxy (E)]]''. 
- Current version is ''1.1.0''  (28 Step. '11)
#br

*** Outline of Functions [#gd1c99c9]
+Texture data caching is enabled through ''[[sl_relay>sl_relay (E)]]''.

***Annoyances or Bugs. [#ie9ebcd0]
+Cache data is saved in a plain file or a Berkeley DB file. SQL database is not supported.
+The speed slows in Berkeley DB. Plain file is more high-speed now. 
+The program has not been stress tested.

** Explanation [#y7c7c0f1]
+[[Caching of Texture Data>./Caching]]
+[[Texture Data Base>./Texture DB]]
+[[When the server has two network interfaces or more>/sl_proxy (E)/two or more network interfaces]]
+[[Expire Cache Data>./Expire]]
+[[Log and Debug Mode>./Log and Debug Mode]]
+[[Security>./Security]]

** Configuration [#c7736a3e]
-The default configuration file is ''/usr/local/etc/sl_proxy/sl_cache.conf''. 
-It is also possible to specify other files if ''-f'' option of  ''sl_cache'' is specified.
-Because the configuration file is read before ''sl_cache'' does the switch to the effective user, exec user should be able to be read. 
-The setting of each item is described in the configuration file. Empty lines or lines starting with # are not read.
#br

*** Items [#w5d029f2]
**** Ports for communication with Relay Server [#q6cfd47b]
-[[MinUdpPutPort>./MinUdpPutPort]]
-[[MaxUdpPutPort>./MaxUdpPutPort]]
-[[MinUdpGetPort>./MinUdpGetPort]]
-[[MaxUdpGetPort>./MaxUdpGetPort]]

**** Number of transfer packets [#y4963aa0]
-[[GetPacketNum>./GetPacketNum]]

**** Access Control [#o39c29e0]
-[[Hosts_Allow_File>/sl_proxy (E)/Hosts_Allow_File]]

**** Etc. etc. [#td42a6e9]
-[[Temp_File_Dir>/sl_proxy (E)/Temp_File_Dir]]
-[[MaxIdleTime>/sl_proxy (E)/MaxIdleTime]]
#br

** Execute Options [#nb85999c]
 sl_cache  [-p port_no] [-f config_file] [-u user_name] [-i interface_address]
           [-pid pid_file] [-l [hitrate_logfile]] [-v syslog_level]
           [-xpr [expire_days]] [-lx [expire_logfile]]
           [-fdb] [-d]
           [--version] [--help] [-h]
        
 -p   : port number that Relay Server(sl_relay) connects. default is 8200.
 -f   : configuration file. default is /usr/local/etc/sl_proxy/sl_cahe.conf
 -u   : specify effective user.
 -i   : specify sl_relay side network interface IP address.
        if your server has two or more network interfaces, you need to use this option.
        
 -pid : specify pid file.
 -l   : create hit rate log file. default file name is /var/sl_proxy/sl_cache_hitrate.log
 -v   : level of syslog. default is LOG_INFO (7).
        
 -xpr : execute the cache expire daemon. 
        The expire time can be continuously specified by day unit. default is the 30days.
        the expire demon retrieves at random and deletes data without the access during 
        the specified days.
 -lx  : create cache expire log file. default file name is /var/sl_proxy/sl_expire_cache.log
        
 -fdb : Berkeley DB is used for the data base. default is plane file.
        
 -d   : debug mode. display debug information.
        
 --version  : display Version information.
 --help, -h : display this Help messages.

**Processes [#b015ec30]
*** Data Caching [#i946f8e2]
-There is a two step data save process so that a single process can control the actually data save, thus avoiding file locking problems. 

http://www.nsl.tuis.ac.jp/xoops/modules/xpwiki/?plugin=ref&page=sl_cache&src=sl_cache.png
- [Save Data Process] is ''Cache Put Server''
- [Get Cache Process] is ''Cache Control Process''

« Prev

Backup list of sl_cache (E)
Backup source of sl_cache (E)(No. All)
- 1: 2008-12-21 (Sun) 03:29:18 gambled
- 2: 2009-01-09 (Fri) 00:04:20 iseki
- 3: 2009-01-13 (Tue) 02:56:08 admin
- 4: 2009-03-13 (Fri) 03:15:14 iseki
- 5: 2009-04-29 (Wed) 13:05:22 iseki
- 6: 2010-04-28 (Wed) 00:46:55 admin
- 7: 2010-12-14 (Tue) 00:44:10 admin
- Cur: 2011-09-28 (Wed) 11:29:54 admin

Source of sl_cache (E)

Site Search

Login

Sub Menu

Books

mini Calendar

Who's Online

Access Counter