public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: o1bigtenor <o1bigtenor@gmail.com>
To: Richard Biener <richard.guenther@gmail.com>
Cc: sgk@troutmask.apl.washington.edu, fortran@gcc.gnu.org
Subject: Re: replacing hardware?
Date: Fri, 14 Apr 2023 06:01:46 -0500	[thread overview]
Message-ID: <CAPpdf5_ZJJ4TnvECXA6MCv0Fw3LTvcTnPHf1XDnT9JDcKPYhTQ@mail.gmail.com> (raw)
In-Reply-To: <CAFiYyc26Pq864Z7NJo6gEwd8wSSeSrm14BDS8-hn=1nWA38R7w@mail.gmail.com>

On Fri, Apr 14, 2023 at 1:40 AM Richard Biener via Fortran
<fortran@gcc.gnu.org> wrote:
>
> On Thu, Apr 13, 2023 at 6:43 PM Steve Kargl via Fortran
> <fortran@gcc.gnu.org> wrote:
> >
> > All,
> >
> > The systems that I've used while hacking on gfortran
> > bugs and features are starting to show their age.  I'm
> > in the early stage of put together the wishlist for
> > a budget friendly replacement.  While I'll likely go
> > with a Ryzen7 cpu, NVME M2 drives, and as much memory
> > as I can afford, I'm looking for recommendations for
> > a budget friendly video/gpu card that will allow me to
> > take a deeper dive into openacc/openmp and offloading.
> > Anyone have a suggestion?
>
> I am sofar doing "functional level" testing of offloading with
> a GTX 1650 which is I think the most affordable thing you
> can still get.  Not sure how future proof this will be though
> with future support from NVIDIA (you still need CUDA for
> offloading).  I have not yet had success with any consumer
> AMD graphics product, the gcn backend requires
> the radeon instinct compute cards.
>
> So I suppose any "cheap" nvidia will do, of course
> performance wise it will suck (esp. when doing FP64 - also
> watch out if they eventually disable that completely on
> some consumer card generations)
>
>
That's problematic as Nvidia's support for open source is
at best spotty and if you're doing something a tiny bit out
of 'usual' - - - - terrible.

My previous system I started using 3 - 570 nvidia gpus and
when 2 failed some 8 years i I replaced them using only 1 -  1650 Ti.
My issue was that I wanted to using a HDMI monitor as part of
my group - - - - - the results were a system that would need a restart
every 2 weeks and it was a royal PITA with the nuisance.
My present system is quite more reliable but today's browsers
are now also increasing the issues - - - - argh!!!!!

HTH

  reply	other threads:[~2023-04-14 11:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-13 16:43 Steve Kargl
2023-04-14  6:40 ` Richard Biener
2023-04-14 11:01   ` o1bigtenor [this message]
2023-04-15  1:37 ` Jerry D
     [not found] <mailman.2280.1681460310.1979823.fortran@gcc.gnu.org>
2023-04-14 12:44 ` Roland Hughes

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAPpdf5_ZJJ4TnvECXA6MCv0Fw3LTvcTnPHf1XDnT9JDcKPYhTQ@mail.gmail.com \
    --to=o1bigtenor@gmail.com \
    --cc=fortran@gcc.gnu.org \
    --cc=richard.guenther@gmail.com \
    --cc=sgk@troutmask.apl.washington.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).