Results 1 to 1 of 1
  1. #1
    jack12 is offline Member
    Join Date
    Oct 2016
    Posts
    29
    Rep Power
    0

    Default Which strategy is optimal for application with few instances with large memory size

    Large memory size with few instances (i.e. machines) tends to be expensive than with small memory size, a greater number of instances. Here is simple math, based on the cost of an AWS EC2 instances in US East (N. Virginia) region:

    m4.16xlarge – 256GB RAM – Linux on-demand instance cost: $3.2/hour

    T3a small – 2GB RAM – Linux on-demand instance cost: $0.0188/hour

    So, to have capacity of 256GB RAM, we would have to get 128 ‘T3a small’ instance (i.e. 128 instances x 2GB = 256GB).

    128 x T3a small – 2GB RAM – Linux on-demand instance cost: $2.4064/hour (i.e. 128 x $0.0188/hour)

    Please go through our blog to know more in detail about Large or small memory size for my App
    Last edited by Norm; 07-05-2019 at 01:08 PM. Reason: Removed link

Similar Threads

  1. Replies: 3
    Last Post: 02-27-2017, 03:20 PM
  2. ImageIO Memory Issue for large images
    By AndrewM16921 in forum Advanced Java
    Replies: 2
    Last Post: 12-29-2014, 09:22 AM
  3. Replies: 0
    Last Post: 10-14-2013, 11:37 AM
  4. Parsing Large PDF :Out of Memory Exception
    By murthybhat in forum Advanced Java
    Replies: 5
    Last Post: 11-03-2009, 05:08 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •