maria-discuss team mailing list archive
-
maria-discuss team
-
Mailing list archive
-
Message #01957
Re: MariaDB 10.1 uses huge amount of memory onWndows
-
From:
Reindl Harald <h.reindl@xxxxxxxxxxxxx>
-
Date:
Sat, 22 Nov 2014 11:58:30 +0100
-
Cc:
Maria Discuss <maria-discuss@xxxxxxxxxxxxxxxxxxx>
-
In-reply-to:
<CAFa9YRCFZTY2MDx4D4HkQeCXoZxD=q5pg=pR4+bNt4xQej7Y1g@mail.gmail.com>
-
Openpgp:
id=7F780279; url=http://arrakis.thelounge.net/gpg/h.reindl_thelounge.net.pub.txt
-
Organization:
the lounge interactive design
-
User-agent:
Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0
Am 22.11.2014 um 11:50 schrieb Peter Laursen:
My Windows installation does not have virtual memory as I turned it off
virtual memory != swap, please don't discuss on that level until
you understand basic operation system tasks, a prerequisite to
talk about memory usage at all
http://en.wikipedia.org/wiki/Virtual_memory
just the fact that you try to compare memory usage outputs of Unix and
Windows 1:1.... no better i don't say the rest
(I don't need it as I have sufficient physical memory not to have it). I
have now set InnoDB buffer size to 1G for MySQL 5.6 5.7 as well as
Maria DB 10.0 and 10.1. That is more than enough for my needs. The
MariaDB instances now show total allocated memory ~2.5 G (5.5. and 10.0)
and ~1.5 G (10.1). The MySQL instances ~1.5 G.
there is a ton of other tuneables
query_cache_limit = 512K
query_cache_min_res_unit = 1K
query_cache_size = 128M
query_cache_type = 1
table_cache = 15000
thread_cache_size = 600
table_definition_cache = 768
tmp_table_size = 512M
max_heap_table_size = 512M
key_buffer_size = 256M
sort_buffer_size = 320K
read_rnd_buffer_size = 256K
join_buffer_size = 320K
read_buffer_size = 128K
preload_buffer_size = 128K
myisam_sort_buffer_size = 128M
innodb_buffer_pool_size = 5120M
innodb_buffer_pool_instances = 5
innodb_purge_threads = 1
innodb_max_purge_lag = 200000
innodb_max_dirty_pages_pct = 60
innodb_additional_mem_pool_size = 32M
innodb_log_file_size = 512M
innodb_log_buffer_size = 256M
innodb_thread_concurrency = 0
innodb_thread_sleep_delay = 10
innodb_flush_log_at_trx_commit = 2
innodb_support_xa = 1
innodb_lock_wait_timeout = 50
innodb_table_locks = 0
innodb_checksums = 0
innodb_file_format = barracuda
innodb_file_per_table = 1
innodb_open_files = 600
innodb_io_capacity = 400
innodb_read_io_threads = 4
innodb_write_io_threads = 4
innodb_doublewrite = 1
innodb_adaptive_flushing_method = keep_average
innodb_flush_method = ALL_O_DIRECT
innodb_stats_on_metadata = 0
transaction-isolation = READ-COMMITTED
On Sat, Nov 22, 2014 at 11:33 AM, Reindl Harald <h.reindl@xxxxxxxxxxxxx
<mailto:h.reindl@xxxxxxxxxxxxx>> wrote:
Am 22.11.2014 um 11:08 schrieb Peter Laursen:
On a side-remark (if someone is interested) the numbers displayed in
Task Manager for the VM running SuSE with MariaDB 10.0.9 must be
incorrect (ther is a full OS runnnig and with a lot of server
programs -
LDAP, Apache etc. etc.). It seems that Windows does not get true
information from the VM process. Also when task manager
displays 19-20
GB of memory use in total, Windows will start complaining that it is
about to run of of memory and programs should be closed So it seems
that around 10 GB memory used by VMs are unaccounted for when it
happens.
windows has alsao the concept of virtual, shared and real memory and
thes same problem as unix telling how how much an application is
using because that mix
the real problem of that thtead is that you *must not* compare two
mysql/mariadb installations until you made 100% sure they are using
the same buffer and cache configuration and have the same dataaset
and uptime
Attachment:
signature.asc
Description: OpenPGP digital signature
Follow ups
References