Difference between revisions of "FreeSWITCH DB In RAMdrive"

From FreeSWITCH Wiki
Jump to: navigation, search
(See Also)
(Discussion)
Line 5: Line 5:
 
=Discussion=
 
=Discussion=
  
Some Linux distros have quirks that cause SQLite to behave poorly when scaling up.  In other cases, disk I/O becomes a bottleneck to FreeSWITCH performance. Putting the FreeSWITCH db files onto a RAM disk can increase performance.
+
Some Linux distros have quirks that cause SQLite to behave poorly when scaling up.  In other cases, disk I/O becomes a bottleneck to FreeSWITCH performance. Putting the FreeSWITCH core.db file onto a RAM disk can increase performance.
  
NOTE: The voicemail db information is also stored on the RAM disk, so be sure to back that up if you plan on restarting your system.
+
To do so, use  the documented setting in switch.conf.xml:
 +
 
 +
    <param name="core-db-name" value="/usr/local/freeswitch/ramdisk" />
  
 
=Example=
 
=Example=

Revision as of 21:47, 21 September 2012

Contents

Introduction

Moving the ephemeral databases to a RAM disk will greatly improve performance, and it is CRITICAL to move them to a RAM disk if you use SSDs. More info on running FreeSWITCH on SSDs is here.

Discussion

Some Linux distros have quirks that cause SQLite to behave poorly when scaling up. In other cases, disk I/O becomes a bottleneck to FreeSWITCH performance. Putting the FreeSWITCH core.db file onto a RAM disk can increase performance.

To do so, use the documented setting in switch.conf.xml:

   <param name="core-db-name" value="/usr/local/freeswitch/ramdisk" />

Example

   mkdir /ram
   mount -t tmpfs tmpfs /ram
   cd /usr/local/freeswitch
   mv db db.old
   ln -s /ram db
   then restart FreeSWITCH

See Also

Performance_testing_and_configurations#FreeSWITCH.27s_core.db_I.2FO_bottleneck