4 ms·

Sorry, is this true? Last days I spent a lot of time going crazy because our apps are consuming 90% of memory on our instances and I feel bad/scary for that.

• praptak 6y ago
  The principle is true and follows from the rule that no resource should be idle if there are requests that need it to be processed. Memory, however is seldom the bottleneck. This is because most apps are not designed to queue requests if they don't fit in the available memory - they just allocate until they fail. So, unless your apps are designed to queue requests in order to fit them into memory, this principle is probably not the explanation for the high memory usage.
• sokoloff 6y ago
  At a minimum, you have to define max correctly. That’s not 100.00% of RAM bytes or CPU cycles and is probably under 25% of Ethernet networks for example.
• dsr_ 6y ago
  Two questions you need to answer: 1. Is the app breaking or failing or not serving its purpose in any way? First find the problem, then look for the causes. 2. Let's say your app is using 29G of the memory in a 32GB instance. If you put it in a 64GB instance, will it use 29GB of that, 63GB of that, or does it continue to grow until it runs out of memory and restarts? The first case means you have correctly sized your instance. The second case means the app is good about using almost but not quite all the memory available. The third case is a problem.
  • 101008 6y ago
    The app is not breaking for now, but it will if we send more requests. The problem we are facing is that if we keep adding more instances (we are using Azure web app) the other instsancs also consume 80% (I thought the original memory consumption would be split equally on all instances). So it seems it is the second case.