[Maria-discuss] MariaDB 10.1 uses huge amount of memory onWndows
Please see attached imaged - a screenshot of Windows Task manager. I have a lot of MySQL and MariaDB servers installed (all needed for application testing). It is noticeable that MariaDB 10.1 uses around twice as much as much memory as compared to MariaDB 10.0, MySQL 5.6 and 5.7 (5 GB versus 2.5 GB in rough numbers). Even more surprising to me as P_S is not running with 10.1 (as I understand). Further I have MariaDB 10.0 running virtualized in OpenSuSE 12.3 inside Virtualbox. The process for the virtual machine use only around 10% or memory as compared to MariaDB 10.0 running natively on Windows (there is also an active VM running Mint Linux - but MySQL is not running there currently) I also have a number of older MySQL servers (5.0, 5.1 and 5.5) The use much less memory. That is expected as the configuration reserves smaller buffers. Both MariaDB servers in Windows use the configuration created by the installer. MySQL 5.6 adn 57 servers use the MySQL Installer standard "developer machine" configuration. The configuraiton of MariaDB 10 in SuSE is as shipped with the distro (I did not check it actually). None of the servers have been connected to since system was restarted. System has been running for approximately 4 hours and all servers start with Windows. The VM with SuSE has been running for approxmately 2 hours. In the attached image I have framed and starred my observations. I want to emphatize, that I don't face any problems with this at all. I have 32 GB RAM and 4 CPUs each capable of processing 2 parallel threads,and I can run Windows 7 with all the servers you see (and simultaneously use the system iinteractively for Internet browsing, playing media, processing photos, document creation/editing and what else you would do with a desktop system), as well as have the two VMs (both configured with an upper resource limit of 24 GB RAM and 6 CPU threads). The memory may be released if it is required by other processes. I don't think it is a problem to use memory if it is available if it will be released when it is required elsewhere (on the opposite it was a little expensive, so it would be a shame if it was not used at all!) But still I find the find the MariaDB 10.1 number for memory use so much *off* as compared to comparable servers, that I think I should mention the observation here. IMO it should be understood **why** it happens and next it can be decided **if** a fix is necessary or not. -- Peter -- Webyog
MSI installation defaults to 1/8 of RAM for the Innodb bufferpool. You can change this value during the installation, see the screenshot is under "Other database properties'" section in https://mariadb.com/kb/en/mariadb/documentation/getting-started/binary-packa... On 11/21/14 21:45, Peter Laursen wrote:
Please see attached imaged - a screenshot of Windows Task manager.
I have a lot of MySQL and MariaDB servers installed (all needed for application testing). It is noticeable that MariaDB 10.1 uses around twice as much as much memory as compared to MariaDB 10.0, MySQL 5.6 and 5.7 (5 GB versus 2.5 GB in rough numbers). Even more surprising to me as P_S is not running with 10.1 (as I understand).
Further I have MariaDB 10.0 running virtualized in OpenSuSE 12.3 inside Virtualbox. The process for the virtual machine use only around 10% or memory as compared to MariaDB 10.0 running natively on Windows (there is also an active VM running Mint Linux - but MySQL is not running there currently)
I also have a number of older MySQL servers (5.0, 5.1 and 5.5) The use much less memory. That is expected as the configuration reserves smaller buffers.
Both MariaDB servers in Windows use the configuration created by the installer. MySQL 5.6 adn 57 servers use the MySQL Installer standard "developer machine" configuration. The configuraiton of MariaDB 10 in SuSE is as shipped with the distro (I did not check it actually).
None of the servers have been connected to since system was restarted. System has been running for approximately 4 hours and all servers start with Windows. The VM with SuSE has been running for approxmately 2 hours.
In the attached image I have framed and starred my observations.
I want to emphatize, that I don't face any problems with this at all. I have 32 GB RAM and 4 CPUs each capable of processing 2 parallel threads,and I can run Windows 7 with all the servers you see (and simultaneously use the system iinteractively for Internet browsing, playing media, processing photos, document creation/editing and what else you would do with a desktop system), as well as have the two VMs (both configured with an upper resource limit of 24 GB RAM and 6 CPU threads).
The memory may be released if it is required by other processes. I don't think it is a problem to use memory if it is available if it will be released when it is required elsewhere (on the opposite it was a little expensive, so it would be a shame if it was not used at all!)
But still I find the find the MariaDB 10.1 number for memory use so much *off* as compared to comparable servers, that I think I should mention the observation here. IMO it should be understood **why** it happens and next it can be decided **if** a fix is necessary or not.
-- Peter -- Webyog
_______________________________________________ Mailing list: https://launchpad.net/~maria-discuss Post to : maria-discuss@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp
Well,you are right -- 10.0: ===== SHOW VARIABLES LIKE 'innodb_buffer%' Variable_name VALUE ----------------------------------- ---------------- innodb_buffer_pool_dump_at_shutdown OFF innodb_buffer_pool_dump_now OFF innodb_buffer_pool_filename ib_buffer_pool innodb_buffer_pool_instances 8 innodb_buffer_pool_load_abort OFF innodb_buffer_pool_load_at_startup OFF innodb_buffer_pool_load_now OFF innodb_buffer_pool_populate OFF innodb_buffer_pool_size 2133852160 [mysqld] datadir=C:/Program Files/MariaDB 10.0/data port=3313 sql_mode="STRICT_TRANS_TABLES,NO_ENGINE_SUBSTITUTION" default_storage_engine=innodb innodb_buffer_pool_size=2035M innodb_log_file_size=50M [client] port=3313 -- 10.1 ===== SHOW VARIABLES LIKE 'innodb_buffer%' Variable_name VALUE ----------------------------------- ---------------- innodb_buffer_pool_dump_at_shutdown OFF innodb_buffer_pool_dump_now OFF innodb_buffer_pool_filename ib_buffer_pool innodb_buffer_pool_instances 8 innodb_buffer_pool_load_abort OFF innodb_buffer_pool_load_at_startup OFF innodb_buffer_pool_load_now OFF innodb_buffer_pool_populate OFF innodb_buffer_pool_size 4289724416 [mysqld] datadir=C:/Program Files/MariaDB 10.1/data port=3314 sql_mode="STRICT_TRANS_TABLES,NO_ENGINE_SUBSTITUTION" default_storage_engine=innodb innodb_buffer_pool_size=4091M innodb_log_file_size=50M character-set-server=utf8 [client] port=3314 I did not notice the setting during installaton. IMO it is a rather aggressive settng for a desktop/developer/application testing system from 10.1. But of course I should have compared configurations. (BTW - SuSe 12.3 skips this config with no explicit innodb buffer pool setting (commented lines removed): [client] # this section is empty [mysqld] innodb_file_format=Barracuda innodb_file_per_table=ON sql_mode=NO_ENGINE_SUBSTITUTION,STRICT_TRANS_TABLES [mysqld_multi] mysqld = /usr/bin/mysqld_safe mysqladmin = /usr/bin/mysqladmin log = /var/log/mysqld_multi.log # details for multi instances all commented here !includedir /etc/my.cnf.d # my.cnf.d contains load statements to plugin .so's for blackhole, federated and archive engines - all commented out.) ..so it is all explained. But I think such setting should be more visible in the installer interface, in particular since it seems to have been changed between 10.0 and 10.1. But not a big issue of course. -- Peter On Fri, Nov 21, 2014 at 10:57 PM, Vladislav Vaintroub <vvaintroub@gmail.com> wrote:
MSI installation defaults to 1/8 of RAM for the Innodb bufferpool. You can change this value during the installation, see the screenshot is under "Other database properties'" section in https://mariadb.com/kb/en/mariadb/documentation/getting-started/binary-packa...
On 11/21/14 21:45, Peter Laursen wrote:
Please see attached imaged - a screenshot of Windows Task manager.
I have a lot of MySQL and MariaDB servers installed (all needed for application testing). It is noticeable that MariaDB 10.1 uses around twice as much as much memory as compared to MariaDB 10.0, MySQL 5.6 and 5.7 (5 GB versus 2.5 GB in rough numbers). Even more surprising to me as P_S is not running with 10.1 (as I understand).
Further I have MariaDB 10.0 running virtualized in OpenSuSE 12.3 inside Virtualbox. The process for the virtual machine use only around 10% or memory as compared to MariaDB 10.0 running natively on Windows (there is also an active VM running Mint Linux - but MySQL is not running there currently)
I also have a number of older MySQL servers (5.0, 5.1 and 5.5) The use much less memory. That is expected as the configuration reserves smaller buffers.
Both MariaDB servers in Windows use the configuration created by the installer. MySQL 5.6 adn 57 servers use the MySQL Installer standard "developer machine" configuration. The configuraiton of MariaDB 10 in SuSE is as shipped with the distro (I did not check it actually).
None of the servers have been connected to since system was restarted. System has been running for approximately 4 hours and all servers start with Windows. The VM with SuSE has been running for approxmately 2 hours.
In the attached image I have framed and starred my observations.
I want to emphatize, that I don't face any problems with this at all. I have 32 GB RAM and 4 CPUs each capable of processing 2 parallel threads,and I can run Windows 7 with all the servers you see (and simultaneously use the system iinteractively for Internet browsing, playing media, processing photos, document creation/editing and what else you would do with a desktop system), as well as have the two VMs (both configured with an upper resource limit of 24 GB RAM and 6 CPU threads).
The memory may be released if it is required by other processes. I don't think it is a problem to use memory if it is available if it will be released when it is required elsewhere (on the opposite it was a little expensive, so it would be a shame if it was not used at all!)
But still I find the find the MariaDB 10.1 number for memory use so much *off* as compared to comparable servers, that I think I should mention the observation here. IMO it should be understood **why** it happens and next it can be decided **if** a fix is necessary or not.
-- Peter -- Webyog
_______________________________________________ Mailing list: https://launchpad.net/~maria-discuss Post to : maria-discuss@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp
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. For the SuSE 12.3/MariaDB 10.0.9 instance InnoDB buffer details are : SHOW VARIABLES LIKE 'innodb_buffer%' Variable_name VALUE ----------------------------------- ---------------- innodb_buffer_pool_dump_at_shutdown OFF innodb_buffer_pool_dump_now OFF innodb_buffer_pool_filename ib_buffer_pool innodb_buffer_pool_instances 8 innodb_buffer_pool_load_abort OFF innodb_buffer_pool_load_at_startup OFF innodb_buffer_pool_load_now OFF innodb_buffer_pool_populate OFF innodb_buffer_pool_size 134217728 (= 128M) -- Peter On Fri, Nov 21, 2014 at 11:35 PM, Peter Laursen <peter_laursen@webyog.com> wrote:
Well,you are right
-- 10.0: =====
SHOW VARIABLES LIKE 'innodb_buffer%'
Variable_name VALUE ----------------------------------- ---------------- innodb_buffer_pool_dump_at_shutdown OFF innodb_buffer_pool_dump_now OFF innodb_buffer_pool_filename ib_buffer_pool innodb_buffer_pool_instances 8 innodb_buffer_pool_load_abort OFF innodb_buffer_pool_load_at_startup OFF innodb_buffer_pool_load_now OFF innodb_buffer_pool_populate OFF innodb_buffer_pool_size 2133852160
[mysqld] datadir=C:/Program Files/MariaDB 10.0/data port=3313 sql_mode="STRICT_TRANS_TABLES,NO_ENGINE_SUBSTITUTION" default_storage_engine=innodb innodb_buffer_pool_size=2035M innodb_log_file_size=50M [client] port=3313
-- 10.1 =====
SHOW VARIABLES LIKE 'innodb_buffer%'
Variable_name VALUE ----------------------------------- ---------------- innodb_buffer_pool_dump_at_shutdown OFF innodb_buffer_pool_dump_now OFF innodb_buffer_pool_filename ib_buffer_pool innodb_buffer_pool_instances 8 innodb_buffer_pool_load_abort OFF innodb_buffer_pool_load_at_startup OFF innodb_buffer_pool_load_now OFF innodb_buffer_pool_populate OFF innodb_buffer_pool_size 4289724416
[mysqld] datadir=C:/Program Files/MariaDB 10.1/data port=3314 sql_mode="STRICT_TRANS_TABLES,NO_ENGINE_SUBSTITUTION" default_storage_engine=innodb innodb_buffer_pool_size=4091M innodb_log_file_size=50M character-set-server=utf8 [client] port=3314
I did not notice the setting during installaton. IMO it is a rather aggressive settng for a desktop/developer/application testing system from 10.1. But of course I should have compared configurations.
(BTW - SuSe 12.3 skips this config with no explicit innodb buffer pool setting (commented lines removed):
[client] # this section is empty
[mysqld] innodb_file_format=Barracuda innodb_file_per_table=ON sql_mode=NO_ENGINE_SUBSTITUTION,STRICT_TRANS_TABLES
[mysqld_multi] mysqld = /usr/bin/mysqld_safe mysqladmin = /usr/bin/mysqladmin log = /var/log/mysqld_multi.log # details for multi instances all commented here
!includedir /etc/my.cnf.d # my.cnf.d contains load statements to plugin .so's for blackhole, federated and archive engines - all commented out.)
..so it is all explained. But I think such setting should be more visible in the installer interface, in particular since it seems to have been changed between 10.0 and 10.1. But not a big issue of course.
-- Peter
On Fri, Nov 21, 2014 at 10:57 PM, Vladislav Vaintroub < vvaintroub@gmail.com> wrote:
MSI installation defaults to 1/8 of RAM for the Innodb bufferpool. You can change this value during the installation, see the screenshot is under "Other database properties'" section in https://mariadb.com/kb/en/mariadb/documentation/getting-started/binary-packa...
On 11/21/14 21:45, Peter Laursen wrote:
Please see attached imaged - a screenshot of Windows Task manager.
I have a lot of MySQL and MariaDB servers installed (all needed for application testing). It is noticeable that MariaDB 10.1 uses around twice as much as much memory as compared to MariaDB 10.0, MySQL 5.6 and 5.7 (5 GB versus 2.5 GB in rough numbers). Even more surprising to me as P_S is not running with 10.1 (as I understand).
Further I have MariaDB 10.0 running virtualized in OpenSuSE 12.3 inside Virtualbox. The process for the virtual machine use only around 10% or memory as compared to MariaDB 10.0 running natively on Windows (there is also an active VM running Mint Linux - but MySQL is not running there currently)
I also have a number of older MySQL servers (5.0, 5.1 and 5.5) The use much less memory. That is expected as the configuration reserves smaller buffers.
Both MariaDB servers in Windows use the configuration created by the installer. MySQL 5.6 adn 57 servers use the MySQL Installer standard "developer machine" configuration. The configuraiton of MariaDB 10 in SuSE is as shipped with the distro (I did not check it actually).
None of the servers have been connected to since system was restarted. System has been running for approximately 4 hours and all servers start with Windows. The VM with SuSE has been running for approxmately 2 hours.
In the attached image I have framed and starred my observations.
I want to emphatize, that I don't face any problems with this at all. I have 32 GB RAM and 4 CPUs each capable of processing 2 parallel threads,and I can run Windows 7 with all the servers you see (and simultaneously use the system iinteractively for Internet browsing, playing media, processing photos, document creation/editing and what else you would do with a desktop system), as well as have the two VMs (both configured with an upper resource limit of 24 GB RAM and 6 CPU threads).
The memory may be released if it is required by other processes. I don't think it is a problem to use memory if it is available if it will be released when it is required elsewhere (on the opposite it was a little expensive, so it would be a shame if it was not used at all!)
But still I find the find the MariaDB 10.1 number for memory use so much *off* as compared to comparable servers, that I think I should mention the observation here. IMO it should be understood **why** it happens and next it can be decided **if** a fix is necessary or not.
-- Peter -- Webyog
_______________________________________________ Mailing list: https://launchpad.net/~maria-discuss Post to : maria-discuss@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp
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
My Windows installation does not have virtual memory as I turned it off (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. -- Peter On Sat, Nov 22, 2014 at 11:33 AM, Reindl Harald <h.reindl@thelounge.net> 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
_______________________________________________ Mailing list: https://launchpad.net/~maria-discuss Post to : maria-discuss@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp
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@thelounge.net <mailto:h.reindl@thelounge.net>> 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
@harald .. I really do not understand why you continue this discussion. Can't you understand that the problem has been SOLVED? I also cannot accpet the *tone* here "please don't discuss on that level". , On the opposite I can only understand that you have a much too big **EGO** to interact with other people in a proper way. I asked why MariaDB asked much more memory than comparable servers. Wlad provided the answer: the Maria DB 10.1 Windows installer sets a larger buffer for innodb_buffer_pool_size (and all the other settngs you list don't matter much - except for max_connections if P_S is enabled) Windows Control Panel .. System ..Advanced System Settings .. Performance.. Advanced .. Virtual Memory (translated from Danish Windows interface). Please see attached image. Maybe you should learn a little bit about Windows? There is (only) one disadvantage of this setting: if the system crashes because o fmemory exhaustion, there will be no stack trace saved. . and @harald. I'd like to ask you to ignore my mails to the maling llist for the future. Frankly I have been extremely irritated by you several times before. If the communications channel her was a Forums system and not a mailing list, I would have blocked you long ago. You are EXTREMELY ANNOYING AND IRRITATING! And sometimes very rude too (and not only to me, I have noticed). -- Peter On Sat, Nov 22, 2014 at 11:58 AM, Reindl Harald <h.reindl@thelounge.net> wrote:
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@thelounge.net
<mailto:h.reindl@thelounge.net>> 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
_______________________________________________ Mailing list: https://launchpad.net/~maria-discuss Post to : maria-discuss@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp
.. to some @MariaDB: We need a 'moderator' here! -- Peter On Sat, Nov 22, 2014 at 1:25 PM, Peter Laursen <peter_laursen@webyog.com> wrote:
@harald .. I really do not understand why you continue this discussion. Can't you understand that the problem has been SOLVED? I also cannot accpet the *tone* here "please don't discuss on that level". , On the opposite I can only understand that you have a much too big **EGO** to interact with other people in a proper way. I asked why MariaDB asked much more memory than comparable servers. Wlad provided the answer: the Maria DB 10.1 Windows installer sets a larger buffer for innodb_buffer_pool_size (and all the other settngs you list don't matter much - except for max_connections if P_S is enabled)
Windows Control Panel .. System ..Advanced System Settings .. Performance.. Advanced .. Virtual Memory (translated from Danish Windows interface). Please see attached image. Maybe you should learn a little bit about Windows? There is (only) one disadvantage of this setting: if the system crashes because o fmemory exhaustion, there will be no stack trace saved.
. and @harald. I'd like to ask you to ignore my mails to the maling llist for the future. Frankly I have been extremely irritated by you several times before. If the communications channel her was a Forums system and not a mailing list, I would have blocked you long ago. You are EXTREMELY ANNOYING AND IRRITATING! And sometimes very rude too (and not only to me, I have noticed).
-- Peter
On Sat, Nov 22, 2014 at 11:58 AM, Reindl Harald <h.reindl@thelounge.net> wrote:
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@thelounge.net
<mailto:h.reindl@thelounge.net>> 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
_______________________________________________ Mailing list: https://launchpad.net/~maria-discuss Post to : maria-discuss@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp
Am 22.11.2014 um 13:26 schrieb Peter Laursen:
.. to some @MariaDB: We need a 'moderator' here!
what exactly is your problem? did you read http://en.wikipedia.org/wiki/Virtual_memory before shouting and if not why?
Windows Control Panel .. System ..Advanced System Settings .. Performance.. Advanced .. Virtual Memory (translated from Danish Windows interface). Please see attached image. Maybe you should learn a little bit about Windows?
maybe you *really* should read what "Virtual Memory" is and *no* it is not what a checkbox in some GUI tells you as well as you can't disbale virtual memory on any operating system these days "please don't discuss on that level" was the clear reaction to "i have disabled virtual memory" which you can't - you just disabled swap and that is only *a small* part of the virtual memory concept at all virtual memory is cache, shared memory, real memory, mapped memory and in fact it is nearly impossile to say "application X is now using Y MB of memory" the buffer pool is only *one* thing
On Sat, Nov 22, 2014 at 1:25 PM, Peter Laursen <peter_laursen@webyog.com <mailto:peter_laursen@webyog.com>> wrote:
@harald .. I really do not understand why you continue this discussion. Can't you understand that the problem has been SOLVED? I also cannot accpet the *tone* here "please don't discuss on that level". , On the opposite I can only understand that you have a much too big **EGO** to interact with other people in a proper way. I asked why MariaDB asked much more memory than comparable servers. Wlad provided the answer: the Maria DB 10.1 Windows installer sets a larger buffer for innodb_buffer_pool_size (and all the other settngs you list don't matter much - except for max_connections if P_S is enabled)
Windows Control Panel .. System ..Advanced System Settings .. Performance.. Advanced .. Virtual Memory (translated from Danish Windows interface). Please see attached image. Maybe you should learn a little bit about Windows? There is (only) one disadvantage of this setting: if the system crashes because o fmemory exhaustion, there will be no stack trace saved.
. and @harald. I'd like to ask you to ignore my mails to the maling llist for the future. Frankly I have been extremely irritated by you several times before. If the communications channel her was a Forums system and not a mailing list, I would have blocked you long ago. You are EXTREMELY ANNOYING AND IRRITATING! And sometimes very rude too (and not only to me, I have noticed).
-- Peter
On Sat, Nov 22, 2014 at 11:58 AM, Reindl Harald <h.reindl@thelounge.net <mailto:h.reindl@thelounge.net>> wrote:
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 <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@thelounge.net <mailto:h.reindl@thelounge.net> <mailto:h.reindl@thelounge.net <mailto:h.reindl@thelounge.net>__>> 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
I have no problem now. Wlad explained (@harald: can'tyou read?9 . But a moderator woudd bevery much appreciated here) @harald: please ignore me COMPLETELY from now on. My nerves cannot tolerate you! -- Peter On Sat, Nov 22, 2014 at 1:35 PM, Reindl Harald <h.reindl@thelounge.net> wrote:
Am 22.11.2014 um 13:26 schrieb Peter Laursen:
.. to some @MariaDB: We need a 'moderator' here!
what exactly is your problem?
did you read http://en.wikipedia.org/wiki/Virtual_memory before shouting and if not why?
Windows Control Panel .. System ..Advanced System Settings .. Performance.. Advanced .. Virtual Memory (translated from Danish Windows interface). Please see attached image. Maybe you should learn a little bit about Windows?
maybe you *really* should read what "Virtual Memory" is and *no* it is not what a checkbox in some GUI tells you as well as you can't disbale virtual memory on any operating system these days
"please don't discuss on that level" was the clear reaction to "i have disabled virtual memory" which you can't - you just disabled swap and that is only *a small* part of the virtual memory concept at all
virtual memory is cache, shared memory, real memory, mapped memory and in fact it is nearly impossile to say "application X is now using Y MB of memory"
the buffer pool is only *one* thing
On Sat, Nov 22, 2014 at 1:25 PM, Peter Laursen <peter_laursen@webyog.com
<mailto:peter_laursen@webyog.com>> wrote:
@harald .. I really do not understand why you continue this discussion. Can't you understand that the problem has been SOLVED? I also cannot accpet the *tone* here "please don't discuss on that level". , On the opposite I can only understand that you have a much too big **EGO** to interact with other people in a proper way. I asked why MariaDB asked much more memory than comparable servers. Wlad provided the answer: the Maria DB 10.1 Windows installer sets a larger buffer for innodb_buffer_pool_size (and all the other settngs you list don't matter much - except for max_connections if P_S is enabled)
Windows Control Panel .. System ..Advanced System Settings .. Performance.. Advanced .. Virtual Memory (translated from Danish Windows interface). Please see attached image. Maybe you should learn a little bit about Windows? There is (only) one disadvantage of this setting: if the system crashes because o fmemory exhaustion, there will be no stack trace saved.
. and @harald. I'd like to ask you to ignore my mails to the maling llist for the future. Frankly I have been extremely irritated by you several times before. If the communications channel her was a Forums system and not a mailing list, I would have blocked you long ago. You are EXTREMELY ANNOYING AND IRRITATING! And sometimes very rude too (and not only to me, I have noticed).
-- Peter
On Sat, Nov 22, 2014 at 11:58 AM, Reindl Harald <h.reindl@thelounge.net <mailto:h.reindl@thelounge.net>> wrote:
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
<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@thelounge.net <mailto:h.reindl@thelounge.net> <mailto:h.reindl@thelounge.net
<mailto:h.reindl@thelounge.net>__>> 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
_______________________________________________ Mailing list: https://launchpad.net/~maria-discuss Post to : maria-discuss@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp
Am 22.11.2014 um 15:19 schrieb Peter Laursen:
I have no problem now. Wlad explained (@harald: can'tyou read? .
then you should not have responded the following below which was the reason i tried to point you to "virtual memory" leading to a *smart-ass answer* of you "i disabled virtual memory"
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
no - *that* is the point of virtual memory alloacted != pyhiscally used, any apache fork process on our main server shows 1600 MB virtual memory which is *not* real memory, the difference in that case is (mostly) zend-opcache mmaped memory shared between all the workers the same for MariaDB: virtual memory 9000 MB / resident memory 6000 MB frankly the innodb buffer pool setting alone don't say anything, it's a virtual allocation until it get filled and used over time
But a moderator woudd bevery much appreciated here
because you can't set a filter in your MUA?
@harald: please ignore me COMPLETELY from now on. My nerves cannot tolerate you!
i will do so because you are not worth the time wasted trying to explain you basic technology since you feel attacked by get corrected and react as a smart ass
@Harald .. could you please stop communicating in this thread. I have already asked you (as a person that irritates me) to ignore me and my mails to MariaDB mailing lists for all future. Communicating with you leads nowhere. You only want to prove your big ego tthe world. @moderator .. please help/conclude! -- Peter On Sat, Nov 22, 2014 at 4:45 PM, Reindl Harald <h.reindl@thelounge.net> wrote:
Am 22.11.2014 um 15:19 schrieb Peter Laursen:
I have no problem now. Wlad explained (@harald: can'tyou read? .
then you should not have responded the following below which was the reason i tried to point you to "virtual memory" leading to a *smart-ass answer* of you "i disabled virtual memory"
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
no - *that* is the point of virtual memory
alloacted != pyhiscally used, any apache fork process on our main server shows 1600 MB virtual memory which is *not* real memory, the difference in that case is (mostly) zend-opcache mmaped memory shared between all the workers
the same for MariaDB: virtual memory 9000 MB / resident memory 6000 MB
frankly the innodb buffer pool setting alone don't say anything, it's a virtual allocation until it get filled and used over time
But a moderator woudd bevery much appreciated here
because you can't set a filter in your MUA?
@harald: please ignore me COMPLETELY from now on. My nerves
cannot tolerate you!
i will do so because you are not worth the time wasted trying to explain you basic technology since you feel attacked by get corrected and react as a smart ass
_______________________________________________ Mailing list: https://launchpad.net/~maria-discuss Post to : maria-discuss@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp
blabla, problem solved? 2014-11-22 14:07 GMT-02:00 Peter Laursen <peter_laursen@webyog.com>:
@Harald .. could you please stop communicating in this thread. I have already asked you (as a person that irritates me) to ignore me and my mails to MariaDB mailing lists for all future. Communicating with you leads nowhere. You only want to prove your big ego tthe world.
@moderator .. please help/conclude!
-- Peter
On Sat, Nov 22, 2014 at 4:45 PM, Reindl Harald <h.reindl@thelounge.net> wrote:
Am 22.11.2014 um 15:19 schrieb Peter Laursen:
I have no problem now. Wlad explained (@harald: can'tyou read? .
then you should not have responded the following below which was the reason i tried to point you to "virtual memory" leading to a *smart-ass answer* of you "i disabled virtual memory"
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
no - *that* is the point of virtual memory
alloacted != pyhiscally used, any apache fork process on our main server shows 1600 MB virtual memory which is *not* real memory, the difference in that case is (mostly) zend-opcache mmaped memory shared between all the workers
the same for MariaDB: virtual memory 9000 MB / resident memory 6000 MB
frankly the innodb buffer pool setting alone don't say anything, it's a virtual allocation until it get filled and used over time
But a moderator woudd bevery much appreciated here
because you can't set a filter in your MUA?
@harald: please ignore me COMPLETELY from now on. My nerves
cannot tolerate you!
i will do so because you are not worth the time wasted trying to explain you basic technology since you feel attacked by get corrected and react as a smart ass
_______________________________________________ Mailing list: https://launchpad.net/~maria-discuss Post to : maria-discuss@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp
_______________________________________________ Mailing list: https://launchpad.net/~maria-discuss Post to : maria-discuss@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp
-- Roberto Spadim SPAEmpresarial Eng. Automação e Controle
As I have told 3 times now, wlad explained this. It is related to the MySQlL 10.1 installe rfor Wndows. But what has not been solved is Harald's egocentric desire to espose his own perfection (as it appears in his own mind and *absolutely* nowhere else). I think it is basic *netetiquette* to reply to questions (and not reply to no-questions). If somebody thinks (s)he has something improtant to say, they should start their own thread and PISS OFF from threads of other users. Harald has harassed me for 2+ years now with his stupid and egocentric replies that were not helpfull at all in relation to the question asked (it was always like "see how smart I am - and I am smarter than you"). - Peter On Sat, Nov 22, 2014 at 6:10 PM, Roberto Spadim <roberto@spadim.com.br> wrote:
blabla, problem solved?
2014-11-22 14:07 GMT-02:00 Peter Laursen <peter_laursen@webyog.com>:
@Harald .. could you please stop communicating in this thread. I have already asked you (as a person that irritates me) to ignore me and my mails to MariaDB mailing lists for all future. Communicating with you leads nowhere. You only want to prove your big ego tthe world.
@moderator .. please help/conclude!
-- Peter
On Sat, Nov 22, 2014 at 4:45 PM, Reindl Harald <h.reindl@thelounge.net> wrote:
Am 22.11.2014 um 15:19 schrieb Peter Laursen:
I have no problem now. Wlad explained (@harald: can'tyou read? .
then you should not have responded the following below which was the reason i tried to point you to "virtual memory" leading to a *smart-ass answer* of you "i disabled virtual memory"
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
no - *that* is the point of virtual memory
alloacted != pyhiscally used, any apache fork process on our main server shows 1600 MB virtual memory which is *not* real memory, the difference in that case is (mostly) zend-opcache mmaped memory shared between all the workers
the same for MariaDB: virtual memory 9000 MB / resident memory 6000 MB
frankly the innodb buffer pool setting alone don't say anything, it's a virtual allocation until it get filled and used over time
But a moderator woudd bevery much appreciated here
because you can't set a filter in your MUA?
@harald: please ignore me COMPLETELY from now on. My nerves
cannot tolerate you!
i will do so because you are not worth the time wasted trying to explain you basic technology since you feel attacked by get corrected and react as a smart ass
_______________________________________________ Mailing list: https://launchpad.net/~maria-discuss Post to : maria-discuss@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp
_______________________________________________ Mailing list: https://launchpad.net/~maria-discuss Post to : maria-discuss@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp
-- Roberto Spadim SPAEmpresarial Eng. Automação e Controle
Please, people, note that this fight has flooded a lot of people's mailboxes with non-technical or out-of-topic mails. If the thread continues, this could be a problem for some of us. Regards Federico
That is why asked a 'moderator' to take action here. Harald acts a s psychcohpah (not as an abuse,but in the clinical meainng of the tem.He should manage his ego) -- Peter On Sat, Nov 22, 2014 at 8:57 PM, Federico Razzoli <federico_raz@yahoo.it> wrote:t
Please, people, note that this fight has flooded a lot of people's mailboxes with non-technical or out-of-topic mails. If the thread continues, this could be a problem for some of us.
Regards Federico
_______________________________________________ Mailing list: https://launchpad.net/~maria-discuss Post to : maria-discuss@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp
frankly i have enough of your childish attitude the only one beeing egocentric and abusive in that thread is you and if you are not interested in somebody try to exlain you things just refrain to post on public mailing lists i don't give a damn if you learn something new but given that i don't post often at all on this list piss on somebody elses feet! Am 22.11.2014 um 19:28 schrieb Peter Laursen:
As I have told 3 times now, wlad explained this. It is related to the MySQlL 10.1 installe rfor Wndows. But what has not been solved is Harald's egocentric desire to espose his own perfection (as it appears in his own mind and *absolutely* nowhere else). I think it is basic *netetiquette* to reply to questions (and not reply to no-questions). If somebody thinks (s)he has something improtant to say, they should start their own thread and PISS OFF from threads of other users.
Harald has harassed me for 2+ years now with his stupid and egocentric replies that were not helpfull at all in relation to the question asked (it was always like "see how smart I am - and I am smarter than you").
On Sat, Nov 22, 2014 at 6:10 PM, Roberto Spadim <roberto@spadim.com.br <mailto:roberto@spadim.com.br>> wrote:
blabla, problem solved?
2014-11-22 14:07 GMT-02:00 Peter Laursen <peter_laursen@webyog.com <mailto:peter_laursen@webyog.com>>:
@Harald .. could you please stop communicating in this thread. I have already asked you (as a person that irritates me) to ignore me and my mails to MariaDB mailing lists for all future. Communicating with you leads nowhere. You only want to prove your big ego tthe world.
@moderator .. please help/conclude!
-- Peter
On Sat, Nov 22, 2014 at 4:45 PM, Reindl Harald <h.reindl@thelounge.net <mailto:h.reindl@thelounge.net>> wrote:
Am 22.11.2014 um 15:19 schrieb Peter Laursen:
I have no problem now. Wlad explained (@harald: can'tyou read? .
then you should not have responded the following below which was the reason i tried to point you to "virtual memory" leading to a *smart-ass answer* of you "i disabled virtual memory"
>> 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
no - *that* is the point of virtual memory
alloacted != pyhiscally used, any apache fork process on our main server shows 1600 MB virtual memory which is *not* real memory, the difference in that case is (mostly) zend-opcache mmaped memory shared between all the workers
the same for MariaDB: virtual memory 9000 MB / resident memory 6000 MB
frankly the innodb buffer pool setting alone don't say anything, it's a virtual allocation until it get filled and used over time
But a moderator woudd bevery much appreciated here
because you can't set a filter in your MUA?
@harald: please ignore me COMPLETELY from now on. My nerves cannot tolerate you!
i will do so because you are not worth the time wasted trying to explain you basic technology since you feel attacked by get corrected and react as a smart ass
To focus back on the original question, would it be interesting to define dynamically the buffer pool size on a similar fashion as the Windows installed does when installing MariaDB using packages on Debian/Ubuntu (or other applicable distros that shows dialog when installing packages from an interactive shell) as it already show a dialog for the root password? I think that asking for a similar question as the "Optimize for transactions" of the Windows installer might also be of interest. Le 21/11/2014 22:57, Vladislav Vaintroub a écrit :
MSI installation defaults to 1/8 of RAM for the Innodb bufferpool. You can change this value during the installation, see the screenshot is under "Other database properties'" section in https://mariadb.com/kb/en/mariadb/documentation/getting-started/binary-packa...
participants (6)
-
Federico Razzoli -
Jean Weisbuch -
Peter Laursen -
Reindl Harald -
Roberto Spadim -
Vladislav Vaintroub