cosmo0920
null+****@clear*****
Mon Jan 6 08:39:37 JST 2014
cosmo0920 2014-01-06 08:39:37 +0900 (Mon, 06 Jan 2014) New Revision: 4a9c017ad96ecb5e3d4de5b72981483e6725ad1f https://github.com/groonga/groonga/commit/4a9c017ad96ecb5e3d4de5b72981483e6725ad1f Merged b4e51e9: Merge pull request #147 from cosmo0920/use-Groonga-notation-reference Message: doc tuning: use "Groonga" notation Modified files: doc/source/reference/tuning.txt Modified: doc/source/reference/tuning.txt (+2 -2) =================================================================== --- doc/source/reference/tuning.txt 2014-01-06 08:32:16 +0900 (4b0181e) +++ doc/source/reference/tuning.txt 2014-01-06 08:39:37 +0900 (73e4063) @@ -8,7 +8,7 @@ Tuning Summary ------- -There are some tuning parameters for improving groonga performance or +There are some tuning parameters for improving Groonga performance or handling a large database. Parameters @@ -111,7 +111,7 @@ vm.overcommit_memory This is :ref:`tuning-memory-usage` related parameter. You can handle a database that is larger than your memory and swap by setting -``vm.overcommit_memory`` kernel parameter to 1. 1 means that groonga +``vm.overcommit_memory`` kernel parameter to 1. 1 means that Groonga can always map database files onto memory. It is no problem until groonga touch mapped database files that their size is larger than memory and swap. Groonga recommends the configuration. -------------- next part -------------- HTML����������������������������...Download