[MAGNOLIA-5102] Provide a way to check available memory - don't allow login if it's not enough Created: 06/Jun/13  Updated: 18/Jun/13  Resolved: 11/Jun/13

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: 5.0
Fix Version/s: 5.0

Type: Improvement Priority: Major
Reporter: Daniel Lipp Assignee: Daniel Lipp
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: JPEG File Screen Shot 2013-06-18 at 11.56.03.jpg    
Issue Links:
causality
is causing MAGNOLIA-5115 Memory protection upon login should u... Closed
dependency
is depended upon by MGNLUI-1623 Warn when opening apps once the memor... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:
Sprint: RC 1

 Description   

We'll stop opening apps if free memory is either < 20% of the available memory or if it's less then 100 Mbytes



 Comments   
Comment by Daniel Lipp [ 07/Jun/13 ]

also see http://wiki.magnolia-cms.com/pages/viewpage.action?pageId=67407174&focusedCommentId=67409050#comment-67409050

Comment by Daniel Lipp [ 18/Jun/13 ]

Sample memory screen shot after adding the System.gc() after installation:

  • first bookmark (red bar): fresh tomcat-bundle started
  • second: triggering install on author
  • third: triggering install on public
  • fourth: author finished with install - first System.gc()
  • fifth: public finished with install - second System.gc()
Comment by Jan Haderka [ 18/Jun/13 ]

What is the red line on the chart? Can you also note the time when gc was forced? Thx.

Generated at Mon Feb 12 04:02:00 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.