Tag Info

New answers tagged

0

Based on your "free -m" output, we can rule out the normal Linux pagecache-related memory occupation (this can be seen by the -/+ buffers/cache line, which report 33 MB only as free). However, from your second top I don't see anything wrong at first glace. Can you provide some other top output and also paste here cat /proc/meminfo?


1

As Craig Watson already told, you should not mess with PHP memory limit if not really necessary. Anyway, it is not possible to correctly size the server without a profound understanding of your workload. I suggest you to simulate a realistic load and in the meanwhile to monitor your server resource allocation/usage. For what it matters, 512 MB are very few ...


2

TL;DR - Don't bump your memory limits for the sake of it. For a standard PHP application like WordPress, 128MB is huge and should be enough for 90% of your needs. However, there are a few important facts here: PHP Memory Allocation is per-script/process As per the PHP documentation for the max_memory option: This sets the maximum amount of memory in ...


0

You measure. You run it at your workplace in a VM of similar specs and put a load test on it. Simple like that. Given that any half decent tablet can run visualization that is also not really an issue.


0

In a nutshell, slabs are memory used by the kernel to run your system. They should be considered memory allocated to the OS itself. Read this Wikipedia page for more info.


0

Great definitions in the link below. One strategy is to guesstimate as the first answer and then to keep an eye on page faults. As your page faults increase and as your available memory decreases you know you need to increase the amount of memory available to the VM. VMware should also allow you to set whether or not a VM is limited to the amount of ...


5

SQL Server will hold on to the RAM it allocates, so since it doesn't seem to go above 6-7 GB, I would allocate 8GB for SQL and keep 2-4 GB extra for the OS in this case (SQL always does some tasks outside the memory it allocates for sqlserver.exe. It would be a good idea to put this value (8 GB) in the min memory settings for your sql server instance. This ...


0

Your motherboard or CPU socket pins may be unhealthy. I do recommend using HP RAM for this as well. While you may have identical part numbers, many times those memory lots can be sourced from different manufacturers. Certain combinations may not be compatible. As far as obtaining firmware for your server, try harder. See that "File name"? Google it.


0

For that model you need to use compatible DIMM module from HP. (& latest bios) (HP supported PC3-10600E UDIMM in 1, 2, or 4GB capacities) HP List that for the G6: 4GB (256MB x 8) PC3-10600E, DIMM memory module PartNumber: 501541-001 ...


0

IN3T4GEZBIX is 4GB modules, have you bought 2 x 4GB additional Memory modules or single 8GB module? When you install memory, you will need to install them in a pair to corresponding memory sockets. For example, install 4GB in A1 socket and another 4GB in B1 socket. just checked HP quickspecs and maximum it can take is 16GB ( 4x4GB). On you case, either ...


0

Check Figure 3-9 for memory sockets & Table 3-1 for type of memory modules to install, you can install mixture of memory sizes but only thing you will need to be careful about is how you install them. you will need to install same sized memory in parallel channel. in your case, same memory size in socket A2 & D2, A1 & D1, similarly C0 & F0 ...


0

Did you have memory ballooning in place? If so, the "missing" memory should be the memory reclaimed by the balloon driver. Can you post the output cat /proc/meminfo on the machine with the "missing" memory? EDIT From your /proc/meminfo output, it seems that balloon is at work indeed. Have a look at "DirectMap4k" value: it reports that about 200 GB of RAM ...


0

For Linux: Install mcelog and it will log all errors into /var/log/mcelog.log You can also look at the Linux sysfs, see the EDAC documentation for the relevant information: https://www.kernel.org/doc/Documentation/edac.txt


0

It can help to install mcelog and run it as a daemon, it can help provide better reports. They are still cryptic but there is slightly more information to go with to find the culrpit DIMM. mcelog can also handle real-time issues by disabling pages with excessive memory errors and thus giving you more chance to keep the machine running longer until you can ...


0

It is a feature, even though your messages are persistent, RabbitMQ will keep things in RAM, the reasoning is that if there's enough RAM there's no need to incur the cost of a disk read. RabbitMQ will swap these out to disk under memory pressure (even when it's not a persistent message). Your publishers are blocking due to flow control, you can toggle the ...


1

These errors are coming from the EDAC - Error Detection And Correction edac_mc class of the device. The events that you are receiving are CE events (Correctible Errors). These are indications that a DIMM is beginning to fail. EDAC has not reported any specific information about which memory row or channel it refers to so it's difficult to tell which one to ...


0

I think you're misreading the memory usage a bit. Small actual memory usage can be normal, however in your case more is going on. According to your "free -m" output: The total memory is: 512 MB Used memory: 510 MB Free memory: 1 MB Cached memory: 488 MB Total swap: 512 MB Used swap: 435 MB <-- Worry about that! Free swap: 76 MB Since you are using ...


4

You can use Out-Minidump function for PowerShell: Out-Minidump writes a process dump file with all process memory to disk. This is similar to running procdump.exe with the '-ma' switch. Basic usage: Enable PowerShell script execution via Set-ExecutionPolicy cmdlet. It should be Bypass, Unrestricted or RemoteSigned. Details: If you (or a helpful ...


3

Currently the proc filesystem is not "container aware" in mount namespaces, so tools basing their logic on this will get host-related values instead of container-related values. But a work is in progess, it's called lxc-fs and few releases are available here. This is a user-space workaround that will make possible a bind mount over /proc to get things ...


0

Memory leak of the userspace process would result in the constantly growing amount of memory used by this process. You could just monitor the processes using top in batch mode (however, it seems that top does not support sorting by memory in the batch mode, https://bugzilla.redhat.com/show_bug.cgi?id=547749) As alternative to top, you could also execute ...


4

There appears to be no way around it. LXC uses cgroups to do its RAM-limiting, and non-virtualization aware tools read stats like /proc/meminfo which is not contained within LXC and will output the overall RAM in the system. You can see this behavior with free or top as well when run inside the container. Source: ...


0

There's non way to know if you have a memory leak. You can suppose it, based on your knowledge of the system and programs instead it. I'd check the file /proc/meminfo, taking the value of MemFree and checking it in some intervals of time. If it is always decreasing, after some intervals, I should assert there is a memory leak. cat /proc/meminfo | gawk '{if ...


0

For those (Renan) interested to know what solution I came up with. I've been using a custom bash script to retrieve the memory (Used / Total) and then converting it to a percentage. #!/bin/bash ...


1

As mentioned by Petter H in his answer, the OOM killer has kill qmgr process. Unfortunately the qmgr is the heart of Postfix mail delivery. When you kill the heart then you kill the person that owns it. Postfix maintain qmgr process as persistent one. It shouldn't die unless the master process told it, perhaps for reloading configuration. If qmgr died ...


-1

I've made all windows update on my Windows Server 2012 and I moved to MSSql Server 2014 Express. Now all works great! Thanks to all.



Top 50 recent answers are included