public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Bertini, Denis Dr." <D.Bertini@gsi.de>
To: Tobias Burnus <tobias@codesourcery.com>, Harald Anlauf <anlauf@gmx.de>
Cc: "fortran@gcc.gnu.org" <fortran@gcc.gnu.org>
Subject: Re: Problem setting buffer size for gfortran ( v 11.2)
Date: Fri, 25 Feb 2022 17:28:20 +0000	[thread overview]
Message-ID: <efd042b4e28f40dda66338630f2e471a@gsi.de> (raw)
In-Reply-To: <f29a2a67-10a8-377b-d01d-459d69b56568@codesourcery.com>

Hi Tobias,


So i use now in my submission script the option you were quoting i.e


> srun --export=ALL


which is actually the default as stated in the slurm documentation.

Setting the following environment to change the buffer size in both formatted/unformatted I/O 😎


export GFORTRAN_FORMATTED_BUFFER_SIZE=10000
export GFORTRAN_UNFORMATTED_BUFFER_SIZE=10000
export GFORTRAN_UNBUFFERED_ALL=n

Does not work even on gcc/gfortran 11.2

If i set the same way some environment variables for openMPI,

it is working.

So this is not related to the forwarding of environment variables

with srun.


Are the variables set correct ?

Best,

Denis


________________________________
From: Tobias Burnus <tobias@codesourcery.com>
Sent: Thursday, February 24, 2022 9:20:26 AM
To: Bertini, Denis Dr.; Harald Anlauf
Cc: fortran@gcc.gnu.org
Subject: Re: Problem setting buffer size for gfortran ( v 11.2)

Hi Denis,

On 24.02.22 09:15, Bertini, Denis Dr. via Fortran wrote:
> I can try that but on our cluster we are bound to use
>    srun (slurm).
> Do you know how to use the same functionality with srun
> to set the environment variables.

I didn't – but the manual did: srun --export=...

See: https://slurm.schedmd.com/srun.html#OPT_export_1

Good luck,

Tobias

-----------------
Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 80634 München; Gesellschaft mit beschränkter Haftung; Geschäftsführer: Thomas Heurung, Frank Thürauf; Sitz der Gesellschaft: München; Registergericht München, HRB 106955

  reply	other threads:[~2022-02-25 17:28 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-23 16:10 Bertini, Denis Dr.
2022-02-23 18:26 ` Harald Anlauf
2022-02-23 18:26   ` Harald Anlauf
2022-02-23 20:28   ` Bertini, Denis Dr.
2022-02-23 20:57     ` Harald Anlauf
2022-02-23 20:57       ` Harald Anlauf
2022-02-23 20:59     ` Bertini, Denis Dr.
     [not found]       ` <trinity-9bf94afe-e773-4366-b0b2-ae398de80664-1645651097363@3c-app-gmx-bs49>
2022-02-23 21:23         ` Bertini, Denis Dr.
2022-02-23 21:38           ` Harald Anlauf
2022-02-24  7:57             ` Bertini, Denis Dr.
2022-02-24  8:13               ` Tobias Burnus
2022-02-24  8:15                 ` Bertini, Denis Dr.
2022-02-24  8:20                   ` Tobias Burnus
2022-02-25 17:28                     ` Bertini, Denis Dr. [this message]
     [not found]                       ` <trinity-59001f50-077d-424e-a648-24645944dd0c-1645813711633@3c-app-gmx-bap28>
2022-02-25 20:01                         ` Bertini, Denis Dr.
2022-02-25 20:44                           ` Harald Anlauf
2022-02-25 20:44                             ` Harald Anlauf
2022-02-25 20:53                             ` Bertini, Denis Dr.
2022-02-26  9:20                               ` Thomas Koenig
2022-02-26 15:37                                 ` Bertini, Denis Dr.

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=efd042b4e28f40dda66338630f2e471a@gsi.de \
    --to=d.bertini@gsi.de \
    --cc=anlauf@gmx.de \
    --cc=fortran@gcc.gnu.org \
    --cc=tobias@codesourcery.com \
    /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).