Tag Info

New answers tagged

0

IIRC MongoDB doesn't directly use memory for data, it uses memory mapped files and lets the OS manage how much is loaded via the normal VFS behaviour. Changing per-process limits is unlikely to affect this. You don't state what platform you are using at all, but if you are already using virtualisation could you could run Mongo in its own VM with a RAM ...


1

I must say this is normal and nothing to worry about. This blog tells how target server memory calculated. Please see the forumula below Target1 = Current committed pages of SQL Server + ( Available Physical Memory - min (Total Physical Memory Pages / 20, Available Physical Memory Pages / 2)) ullAvailPageFile: The maximum amount of memory the ...


11

A hefty question :-) I'll outline some of the factors involved. In any given context, these factors and others can vary and produce an interesting result. Sorry I wasn't able to make this much shorter... Accumuated CPU ms vs logical IO SQL Server logical memory node alignment with physical NUMA nodes Spinlock contention in query workspace memory ...


5

(please update your question with coreinfo -v (a sysinternal utility) output to get a better context of your CPU / sockets and NUMA distribution) We looked at overall CPU utilization which was around 60 percent. We did not look at socket specific CPU metrics. I/O metrics were average. Seems to me that you are barking at the wrong tree. SQL Server is ...


0

CREATE TABLE `genescorrelation` ( `correlation` FLOAT NOT NULL, `gene1_id` SMALLINT unsigned NOT NULL, `gene2_id` SMALLINT unsigned NOT NULL, PRIMARY KEY (gene1_id, gene2_id), KEY (gene2_id, gene1_id, correlation) ) ENGINE=InnoDB; and reload. I am assuming that FLOAT, with about 7 significant digits is more than enough for a ...


1

Looking at the query SELECT gene1_id, AVG(correlation) AS avg FROM genescorrelation WHERE gene2_id IN (176829, 176519, 176230) GROUP BY gene1_id ORDER BY NULL I have four(4) suggestions SUGGESTION #1 I see three(3) columns. I recommend making a covering index ALTER TABLE genescorrelation ADD INDEX gene2_gene1_correlation_idx1 ...


2

Bug 11872813 - V$PGA_TARGET_ADVICE VIEW IS EMPTY. After setting PGA_AGGREGATE_TARGET > approximately 12G the V$PGA_TARGET_ADVICE view is empty. This issue will be fixed in version 12.1 and a fix is expected to be included in patch set 11.2.0.4. Apply Patch 11872813



Top 50 recent answers are included