My Task Manager Image
If I restart service then it starts with 4% of RAM, then gradually increases
Related
I have a cube server with 16 virtual core and 64 GB memory. the average usage of memory is around 45% and CPU usage is about 60% max. We have almost 10 cubes on this server.
We are observing whenever we process a cube(any client) the web application which communicates via OLAP site, queries get stuck. All dashboards for any client hang until we kill the cube processing or it is over.
We were experimenting with multiple settings but any guidance will very helpful as we have restless clients on our head.
Tweaking the ThreadPool\Query\Max thread from 0 to 160 did help if the cube is not running. Also if we process the cube with max parallel =8 or 16 we are able to query the dashboard but slower than expected.
We also add following settting in msmdpump config file :
<ConfigurationSettings>
<ServerName>localhost</ServerName>
<SessionTimeout>3600</SessionTimeout>
<ConnectionPoolSize>500</ConnectionPoolSize>
<MaxThreadPoolSize>160</MaxThreadPoolSize>
<MaxThreadsPerClient>60</MaxThreadsPerClient>
</ConfigurationSettings>
Could anyone please help with what is going wrong here and how we can improve it?
I have a SQL Server 2016 Standard Version and often face with
RESERVED_MEMORY_ALLOCATION_EXT
SOS_SCHEDULER_YIELD
MEMORY_ALLOCATION_EXT
wait types. However my server CPU don't exceed 20% and I have always 75 GB freeable memory?
I set MAXDOP value 3 but there is no change. I didn't face with any problem when I was using Enterprise edition with same DB and same queries.
Thank you for help
We exerienced the same today and it was due to a virtualization issue.
We had another VM on the same physical host which ran at 100% CPU and due to overcommitment and missing reservation, the Database VM had to wait for CPU cycles. This is almost impossible to track down from within the Database VM.
I have elastisearch installed on my server size of the which is 10GB roughly, I have 16GB of RAM and 1TB of space. But still there are couple of strange issues that I am unable to understand about elasticsearch.
I have dedicated 10GB of ram to elasticsearch still my shards goes down and shows out of memory error when there is heavy insert operation happening.
Randomly elasticsearch stats using maximum resources of my server as shown shown below as a result server performance is almost dead
I am new to Infinispan. We have setup a Infinispan cluster so that we can make use of the Distributed Cache for our CPU and memory intensive task. We are using UDP as the communication medium and Infinispan MapReduce for distributed processing. The problem we are using facing is with the throughput. When we run the program on a single node machine, the total program completes in around 11 minutes i.e. processing a few hundred thousand records and finally emitting around 400 000 records.
However, when we use a cluster for the same dataset, we are seeing a throughput of only 200 records per second being updated between the nodes in the cluster, which impacts the overall processing time. Not sure which configuration changes are impacting the throughput so badly. I am sure its something to do with the configuration of either JGroups or Infinispan.
How can this be improved?
We are running SQL Server 2005 on 64 bit. The PF Usage reaches close to 25 GB every week. Queries that normally take less than a second to run become very slow during this time. What could be causing this?
After running PerfMon, the two counters, Total Server Memory and Target Server Memory show 20 GB and 29 GB respectively. Processor Queue Length and Disk Queue Length are zero.
Sounds like you don't have enough memory, how much is on the Server? More than your page file?
Also could mean Sql Server has "paged out" meaning Windows decided to swap all the info it stored in memory onto the disk.
Open Perfmon ( Goto a command prompt, and type perfmon ) and add these counters:
SQLServer:Buffer Manager - Buffer cache hit ratio
SQLServer:Buffer Manager - Page life expectancy
SQLServer:Memory Manager - Memory Grants Pending
If Buffer Cache Hit Ratio is < 95% it means Sql is using the disk instead of memory a lot you need more memory.
If your page life expectancy is < 500 it mean SqlServer is not keeping results cached in memory, you need more memory.
If you have a lot of Memory Grants Pending, you need more memory.
There are also two stats which let you know how much memory SqlServer wants and how much its actually using. They are called something like "Total Memory Used" and "Total Memory Requested". If Requested > Used, guess what, you need more memory.
There are also some dmv's you can use to determine if your queries are being held up while waiting for memory to free up. I think its sys_dmv.os_wait_stats, something like that.
I community wikied this so a real dba can come in here and clean this up. Don't know the stats off the top of my head.
This is a great read on how to use DMV's to determine memory consumption on sql: http://technet.microsoft.com/en-us/library/cc966540.aspx - look for the 'memory bottlenecks' section.
One big thing is to determine if the memory pressure is internal to SQL (usually the case) or external (rare, but possible). For example, perhaps nothing is wrong with your server, but a driver installed by your antivirus program is leaking memory.