2. target/query persistence (1)
Norikra does NOT save targets/queries by default.
v1.0.4 warn on log
Use “--stats=PATH” option to save targets/queries on
specified path at shutdown
Targets/queries are loaded automatically after
restarts if “--stats” specified
14年7月9日水曜日
3. target/query persistence (2)
“--dump-stat-interval=N”
Autosave targets/queries every specified interval (not
only on shutdown)
“--stats-secondary=PATH_PATTERN”
Backup stats file path: date pattern available
ex: “/var/norikra/stats.%Y%m%d.json”
14年7月9日水曜日
4. JVM options (1)
GC:
“norikra start” specifies JVM options in default
-XX:-UseGCOverheadLimit
-XX:+UseConcMarkSweepGC -XX:+UseCompressedOops
-XX:CMSInitiatingOccupancyFraction=70
-XX:+UseCMSInitiatingOccupancyOnly
-XX:NewRatio=1
-XX:SurvivorRatio=2 -XX:MaxTenuringThreshold=15
-XX:TargetSurvivorRatio=80
-XX:SoftRefLRUPolicyMSPerMB=200
Use “--bare-jvm” for JVM w/o any options
14年7月9日水曜日
5. JVM options (2)
GC log:
Use “--gc-log=PATH” to get GC logs
-Xloggc:FILE_PATH
-verbose:gc -XX:+PrintGCDetails -XX:+PrintGCDateStamps
-XX:+HeapDumpOnOutOfMemoryError
14年7月9日水曜日
6. JVM options (3)
Any “-X” or “-XX” JVM options are available
ex: “norikra start -Xmx2g”
This makes “norikra start” extremely slow! :(
14年7月9日水曜日
7. “SELECT * FROM ...”
“SELECT * FROM ...” may NOT perform as user
expects
Because “*” requires schema, but Norikra does not
have it
14年7月9日水曜日
8. Query group
Query have 3 string elements:
name, group, statement
“name” is used to fetch its results
“group” is used to sweep results of queries which
have same group name
14年7月9日水曜日
