forked from LunarBaseEngin/LunarBase
-
Notifications
You must be signed in to change notification settings - Fork 1
/
creation.conf
executable file
·158 lines (116 loc) · 5.53 KB
/
creation.conf
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
# ------------------------------------------------------------------------- #
# LunarDB version 0.8.4 #
# (c) neo.carmack@lunarion.com, 2015 #
# #
# *** Configuration file *** #
# #
# -Default values read by LunarDB during initialisation. #
# This file is looked for in #
# 1) default is the current directory #
# 2) or any other place specified by user #
# -Options given on the command-line override the values given in here. #
# -Only runtime tunable option can be changed after database creation. #
# -Other options can be configured before the creation of database, any #
# change on those options at run time leads to unpredictable error. #
# ------------------------------------------------------------------------- #
# ----------------#
# Global settings #
# --------------- #
#deprecated
#root_path=/home/feiben/DBTest/
database_name = RTSeventhDB
port = 30860
linux_X86_native_enabled = yes
multi_process_support_enabled = yes
# --------------------#
# End Global settings #
# ------------------- #
# ----------------#
# runtime tunable #
# --------------- #
# -------------------- memory ---------------------#
# -lunarDB uses parameters as left offset: #
# -1 << $number . #
# -e.g. if bit_buff_length = 25, #
# -the real memeory consumes 1 << 25 = 32M bites, #
# -db restart is required if one needs changes take#
# -effective immediatly #
# ------------------------------------------------ #
bit_buff_length = 15
cache_blocks_in_memory = 15
cache_keys_in_memory = 17
cache_records_in_memory = 12
# ---------------- concurrency --------------------#
# -db restart is required if user needs changes #
# -take effective immediatly #
# ------------------------------------------------ #
internal_cache_concurrent_level = 17
ultimate_socket_concurrent_connections = 1000
# --------------------#
# End runtime tunable #
# ------------------- #
# ---------------- real time mode ------------------------- #
# rt_mode and search_engine_mode can be on or off. #
# --------------------------------------------------------- #
search_engine_mode = off
rt_mode = on
# The memory page size of your system. For most cases, it is 4K = 1<<12 bytes
rt_mem_page_size = 12
# maximum page table entries. Default is 4K = 1<< 12.
# Each entry manages 1024 pages, with page size of 4096 bytes.
# LunarMax internal has 16 tables,
# hence by default, the maximum 256GB = 16 * 4096 * 1024 * 4096 memory can be used.
#
# If rt_virtual_mem_enabled is turned off, LunarMax acquires memory directly from OS,
# and will never use extra swap space to extend the physical memory. The OS takes the responsibility
# to swap in-and-out hot and cold pages. In this mode, LunarMax has no controll of
# how many memory will be used, and will race memory resource with other services
# running on the same server.
#
# If rt_virtual_mem_enabled is on, LunarMax takes the controll of memory consumption.
# For example, set rt_max_memory = 28, then at most 256MB = 1 << 28 physical memory will be used.
# Theoretically on a 64-bit machine, virtual memory has no limitation.
# We strongly suggest locating the swap space (by rt_vm_swap) on a SSD device for quick page exchange.
rt_virtual_mem_enabled = on
rt_max_memory = 28
rt_max_virtual_pte = 12
rt_vm_swap = /home/feiben/DBTest/Swap
# for float data: 0 for integer, 1 for 0.1, 2 for 0.01, 3 for 0.001, and so on.
rt_precision = 3
# threads for real time computation.
# Concerning performance, rt_threads+ internal_cache_concurrent_level
# will never exceeds the threads that OS can provide.
# One column with one thread gives the best practice.
rt_threads = 4
# ------------------------------#
# unchangable after creating #
# ----------------------------- #
# -------------- storage --------------------------#
# -lunarDB uses these parameters as left offset: #
# -1 << $number . #
# -e.g. if mani_file_bit_len = 18, #
# -the memeory consumption then is 1 << 18 = 256K, #
# -db rebuild is required if one need changes of #
# -any storage specifications take effective #
# -immediatly #
# ------------------------------------------------ #
mani_file_bit_len = 28
records_table_file_bit_len = 28
# ------------ file system level ------------------#
# Maximum block level controlls the size of blocks #
# of Lunar virtual file system. #
# -level 0: block size = 64 byte, #
# -level 1: block size = 512 byte, #
# -level 2: block size = 4K byte, #
# -level 3: block size = 32K byte, #
# -level 4: block size = 256K byte, #
# -level 5: block size = 2048K byte, #
# #
# Maximum level 2 serves well for most of the #
# applications with lunardb as their storage #
# and search engine #
# ------------------------------------------------ #
block_ultimate_level = 5
# --------------------------------- #
# End unchangable #
# --------------------------------- #