Search

'메모리'에 해당되는 글 3건

  1. 2018.07.18 램디스크 (Softperfect RamDisk)
  2. 2016.11.14 [MYSQL]DB 튜닝(innodb / my.cnf)
  3. 2010.06.01 Tomcat Unix버전 JAVA메모리

램디스크 (Softperfect RamDisk)

Tips 2018.07.18 15:06 Posted by 애플자라

 

사용방법


1. + 버튼을 눌러주자.

2. 크기에 원하는 만큼의 램 용량을 넣어주자. (자신의 램 용량이 8기가라면 1기가, 16기가라면 2~3기가를 넣어도 좋다. 필자는 32기가라 10기가를 넣었다.)

3. 드라이브 문자를 정해주자. X Y Z 아무거나 써도 좋다.

4. 파일시스템은 NTFS 로 해주자. 아무래도 현재 윈도우에서 사용되는 포맷과 맞춰주는게 좋다.

5. 폴더 생성 부분에는 위 그림처럼 폴더별로 한줄씩 적어주면된다. 부팅시에 그대로 폴더가 생성된다.


생성 끝.


필자는 위 사진이랑은 다르게 Y 드라이브로 마운트 했다.

 

 

ramdisk_setup_3.4.7.exe

 

**** 주의 *****

램디스크라는건 휘발성 램에 데이터를 쓴다는 이야기이다. 즉 재부팅하면 날라가는 부분이라는것.

임시로 사용되는 데이터만 기록할 때 쓰는것이다. 대신 속도가 굉장히 빠르다.


출처: http://haru.kafra.kr/76 [어제도 오늘도 내일도 언제나 하루]

[MYSQL]DB 튜닝(innodb / my.cnf)

Programing 2016.11.14 16:33 Posted by 애플자라

### DB셋팅 / 2016.11.14


# Set the SQL mode to strict
sql-mode="STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION"

 

# The maximum amount of concurrent sessions the MySQL server will
# allow. One of these connections will be reserved for a user with
# SUPER privileges to allow the administrator to login even if the
# connection limit has been reached.
max_connections=1000

 

# Query cache is used to cache SELECT results and later return them
# without actual executing the same query once again. Having the query
# cache enabled may result in significant speed improvements, if your
# have a lot of identical queries and rarely changing tables. See the
# "Qcache_lowmem_prunes" status variable to check if the current value
# is high enough for your load.
# Note: In case your tables change very often or if your queries are
# textually different every time, the query cache may result in a
# slowdown instead of a performance improvement.
query_cache_size=0

 

# The number of open tables for all threads. Increasing this value
# increases the number of file descriptors that mysqld requires.
# Therefore you have to make sure to set the amount of open files
# allowed to at least 4096 in the variable "open-files-limit" in
# section [mysqld_safe]
table_cache=256

 

# Maximum size for internal (in-memory) temporary tables. If a table
# grows larger than this value, it is automatically converted to disk
# based table This limitation is for a single table. There can be many
# of them.
tmp_table_size=369M


# How many threads we should keep in a cache for reuse. When a client
# disconnects, the client's threads are put in the cache if there aren't
# more than thread_cache_size threads from before.  This greatly reduces
# the amount of thread creations needed if you have a lot of new
# connections. (Normally this doesn't give a notable performance
# improvement if you have a good thread implementation.)
thread_cache_size=8

 

#*** MyISAM Specific options

# The maximum size of the temporary file MySQL is allowed to use while
# recreating the index (during REPAIR, ALTER TABLE or LOAD DATA INFILE.
# If the file-size would be bigger than this, the index will be created
# through the key cache (which is slower).
myisam_max_sort_file_size=100G

 

# If the temporary file used for fast index creation would be bigger
# than using the key cache by the amount specified here, then prefer the
# key cache method.  This is mainly used to force long character keys in
# large tables to use the slower key cache method to create the index.
myisam_sort_buffer_size=738M

 

# Size of the Key Buffer, used to cache index blocks for MyISAM tables.
# Do not set it larger than 30% of your available memory, as some memory
# is also required by the OS to cache rows. Even if you're not using
# MyISAM tables, you should still set it to 8-64M as it will also be
# used for internal temporary disk tables.
key_buffer_size=641M

 

# Size of the buffer used for doing full table scans of MyISAM tables.
# Allocated per thread, if a full scan is needed.
read_buffer_size=64K
read_rnd_buffer_size=256K

 

# This buffer is allocated when MySQL needs to rebuild the index in
# REPAIR, OPTIMZE, ALTER table statements as well as in LOAD DATA INFILE
# into an empty table. It is allocated per thread so be careful with
# large settings.
sort_buffer_size=256K

 

# Additional memory pool that is used by InnoDB to store metadata
# information.  If InnoDB requires more memory for this purpose it will
# start to allocate it from the OS.  As this is fast enough on most
# recent operating systems, you normally do not need to change this
# value. SHOW INNODB STATUS will display the current amount used.
innodb_additional_mem_pool_size=26M

 

# If set to 1, InnoDB will flush (fsync) the transaction logs to the
# disk at each commit, which offers full ACID behavior. If you are
# willing to compromise this safety, and you are running small
# transactions, you may set this to 0 or 2 to reduce disk I/O to the
# logs. Value 0 means that the log is only written to the log file and
# the log file flushed to disk approximately once per second. Value 2
# means the log is written to the log file at each commit, but the log
# file is only flushed to disk approximately once per second.
innodb_flush_log_at_trx_commit=1

 

# The size of the buffer InnoDB uses for buffering log data. As soon as
# it is full, InnoDB will have to flush it to disk. As it is flushed
# once per second anyway, it does not make sense to have it very large
# (even with long transactions).
innodb_log_buffer_size=13M

 

# InnoDB, unlike MyISAM, uses a buffer pool to cache both indexes and
# row data. The bigger you set this the less disk I/O is needed to
# access data in tables. On a dedicated database server you may set this
# parameter up to 80% of the machine physical memory size. Do not set it
# too large, though, because competition of the physical memory may
# cause paging in the operating system.  Note that on 32bit systems you
# might be limited to 2-3.5G of user level memory per process, so do not
# set it too high.
innodb_buffer_pool_size=1243M

 

# Size of each log file in a log group. You should set the combined size
# of log files to about 25%-100% of your buffer pool size to avoid
# unneeded buffer pool flush activity on log file overwrite. However,
# note that a larger logfile size will increase the time needed for the
# recovery process.
innodb_log_file_size=622M

 

# Number of threads allowed inside the InnoDB kernel. The optimal value
# depends highly on the application, hardware as well as the OS
# scheduler properties. A too high value may lead to thread thrashing.
innodb_thread_concurrency=18

innodb_lock_wait_timeout = 1200

 

Tomcat Unix버전 JAVA메모리

Linux 2010.06.01 14:29 Posted by 애플자라


[Tomcat Base]Catalina.sh

JAVA_OPTS="$JAVA_OPTS -Xms256m -Xmx512m" 톰캣재구동하였음

'Linux' 카테고리의 다른 글

[Linux].profile  (0) 2010.09.09
[Unix]export LANG=c  (0) 2010.06.23
Tomcat Unix버전 JAVA메모리  (0) 2010.06.01
find grep 파일명 찾기  (0) 2010.01.05
[Linux] 계정,그룹만들기  (0) 2009.10.05
[Unix,Linux] Crontab  (0) 2009.10.05