New answers tagged memory
Memory is not instrumented in MySQL until version 5.7 (currently in development), so this does make your question a bit of a guessing game. I can see from inside InnoDB status, that it doesn't appear to be InnoDB consuming the memory (assuming you collected this from when the problem was occurring): Total memory allocated 26217103360; in additional pool ...
You have to increase the RAM size and the increase the SGA parameters. I would suggest you to go through OTN: https://community.oracle.com/thread/2324835?tstart=0
Depending on what you mean by "Oracle Server", if you are trying to monitor physical (or virtual) server level statistics, you can make use of OSWatcher. http://docs.oracle.com/cd/E37670_01/E37355/html/ol_oswatcher_diag.html Note that this is really just a wrapper of stuff that should be available on any *nix type server. It will format outputs and ...
if you have oracle Diagnostic and/or Tuning pack you can use some of these advisors, eg. by Oracle Enterprise Manager: Diagnostics Pack: Performance (tab) ADDM Tuning Pack: SQL Access Advisor SQL Tuning Advisor You can check this by running: show parameter CONTROL_MANAGEMENT_PACK_ACCESS; Some useful summary of advisors: ...
This is almost certainly memory fragmentation, as redis is well-known and loved in production and you probably haven't found a memory leak. The recommendations about setting the size of the pool won't help fragmentation. You'll have to specifically lower the Redis size - lower than your actual memory size - because Redis can't account for fragmentation - ...
I found out that due to this bug, MySQL 5.6.17 uses 6kb memory per open subpartition. This would result in about 500 GB of memory usage for 100 connections each having 100 tables with 800 partitions each, with 8 subpartitions each.
If you are going to put MySQL in a wimpy environment (WIMP = Windows, IIS, MySQL, PHP/Perl/Python), your first priority needs to be RAM. Please get more RAM on the box.I suggest 32GB. As for MySQL, you need to tune InnoDB as much as possible. Here is the InnoDB Architecture InnoDB Architecture Recommendation #1 By default, 25% of the Buffer Pool is ...
They just released new server & driver packages (7/25/2014). I had the same issue with the old drivers but with the 7/25 release it is gone.
Use the maxmemory to set a limit to how much your Redis database can grow too. Failing to do so, Redis will grow until the OS will kill it once memory is exhausted (per your current experience). The usage of maxmemory should be coupled with maxmemory-policy - you can choose from different eviction policies depending on your use case's requirements. For ...
Top 50 recent answers are included