Just for reference...

[image: image.png]
[image: image.png]
[image: image.png]

t2.medium may be the way to go

On Fri, Jun 5, 2020 at 2:32 PM Matt Sicker <[email protected]> wrote:

> Looks like m5a are AMD and t2 are Intel (and burstable). If they cost
> similar, m5a sounds better.
>
> On Fri, Jun 5, 2020 at 4:19 PM Vlad Silverman <[email protected]>
> wrote:
> >
> > I don't know what the cost difference is between the t2 and m5a
> instances.
> >
> >
> > I guess it depends on the region.
> > More details are at https://aws.amazon.com/ec2/pricing/on-demand/
> >
> > On Jun 5, 2020, at 2:02 PM, Slide <[email protected]> wrote:
> >
> > We are currently using t2.small instances on EC2 for the non-high memory
> instances
> >
> > <image.png>
> >
> > Going from t2.small to t2.medium would double the CPU Credits / hour,
> though it also doubles vCPU count and Mem.
> >
> > The high mem instances are using m5.adxlarge:
> >
> > <image.png>
> >
> > I don't know what the cost difference is between the t2 and m5a
> instances.
> >
> > On Fri, Jun 5, 2020 at 1:40 PM Basil Crow <[email protected]> wrote:
> >>
> >> On Fri, Jun 5, 2020 at 1:24 PM Jesse Glick <[email protected]>
> wrote:
> >> > The next step would be PRs to infrastructure repositories.
> >>
> >> I agree. Unfortunately I have spent too much time on this issue already
> and
> >> cannot volunteer to become an infrastructure developer at present.
> >>
> >> > 256Mb seems low for a Surefire JVM—this needs to run Jenkins and all
> >> > plugins plus whatever your test code is doing.
> >>
> >> I agree, which is why I said "I worked around the problem" rather than
> "I
> >> solved the problem." Changing the JVM settings for Surefire and the
> agent
> >> launched by my tests was easy because both those JVMs were completely
> within
> >> my control. I agree that a long-term solution would involve setting
> -Xmx and
> >> -Xms on all agent and Maven JVMs as well as possibly increasing the EC2
> >> instance size for these nodes.
> >>
> >> --
> >> You received this message because you are subscribed to the Google
> Groups "Jenkins Developers" group.
> >> To unsubscribe from this group and stop receiving emails from it, send
> an email to [email protected].
> >> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CAFwNDjrjW2aA74pqoFMhca%2BD0YqL%3DWvNe46g7G1aM3Bmx5LrWQ%40mail.gmail.com
> .
> >
> >
> >
> > --
> > Website: http://earl-of-code.com
> >
> > --
> > You received this message because you are subscribed to the Google
> Groups "Jenkins Developers" group.
> > To unsubscribe from this group and stop receiving emails from it, send
> an email to [email protected].
> > To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CAPiUgVfTTqU65LN7iDo%2BMw5xPnCKFJfiTqq7kgcCtfXVMsN42w%40mail.gmail.com
> .
> >
> >
> > --
> > You received this message because you are subscribed to the Google
> Groups "Jenkins Developers" group.
> > To unsubscribe from this group and stop receiving emails from it, send
> an email to [email protected].
> > To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/FCEB4838-4FF8-410F-AEB3-6FACBDF98D80%40gmail.com
> .
>
>
>
> --
> Matt Sicker
> Senior Software Engineer, CloudBees
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CAEot4ox0q94X6DA-iyhNwoEXXwZk98E5qN1da0ngO6XWCre2Vw%40mail.gmail.com
> .
>


-- 
Website: http://earl-of-code.com

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAPiUgVdB%2B1Yde21oead4b_BdfZS79C0af61__bMKC%2BtiXsNTLQ%40mail.gmail.com.

Reply via email to