New answers tagged

0

Purely from a hardware perspective, manangement of main memory form the Nehalem architecture onwards is management by an integrated memory controller, this is on the "Un-core" part of the CPU die which is seperate from the part which the actual cores live on, because memory is effectively 'Wired' to each CPU, foreign memory access AFAIK is via the quick path ...


0

Manangement of main memory form the Nehalem architecture onwards is management by an integrated memory controller, this is on the "Un-core" part of the CPU die which is seperate from the part which the actual cores live on, because memory is effectively 'Wired' to each CPU, foreign memory access AFAIK is via the quick path interconnect ( again from Nehalem ...


2

Your key_buffer, innodb_buffer_pool and innodb_log_buffer together already exhausts the available memory in a a t2 instance. If you also consider the per thread allocations (>3M) * 70 (max connections) the possible usage is growing by another 210M minimum. You have 270MB InnoDb data. If you don't expect it to grow significantly over time almost 600MB ...


8

My problem is that my server is going over the set 12GB memory and if things like CLR/Full Text/Server exe files taking additional memory. What Denny Cherry wrote is true for SQL Server version from 2005 to 2008 r2. From SQL Server 2012 onward there was considerable change in SQL Server memory allocation. Memory for SQLCLR is allocated from max server ...


7

There's no exact way to do this. The setting you apply to max server memory only manages some of SQL Server's memory, it will still use other allocations depending on what you're doing. To limit this you can minimize your usage of things that use memory external to this (CLR, full text, etc), but you can't eliminate all of it. You can play with max server ...


0

From the output you posted I can see MEMORYCLERK_SQLQERESERVATIONS 39874 (MB) The value is 38G which is huge. Why is SQL Server operations(sortand hash) requesting so much memory What is SQLRESERVATIONS SQL Server memory allocated during query execution for Sort and Hash operations. Do you really think 38 G is what the sort and hash operations ...


0

If you're running 5.6+ you can have the server dump and preload the buffer pool by adding a couple of settings to my.cnf, rather than waiting for it to warm up after each restart. innodb_buffer_pool_dump_at_shutdown=ON innodb_buffer_pool_load_at_startup=ON https://dev.mysql.com/doc/refman/5.6/en/innodb-preload-buffer-pool.html


2

Fool that I am... the server was restarted this morning. I realized this as I was finishing the question. The buffer pool won't fill up until the database actually needs to use that much data. Indeed, if I re-run the buffer pool query I can see the "Free buffers" number slowly decrease. I could run some queries to force tables into memory, but given I know ...



Top 50 recent answers are included