Am Mittwoch, den 31.08.2011, 16:55 +0200 schrieb robert:
> Am Mittwoch, den 31.08.2011, 08:46 -0600 schrieb John Peterson:
> > On Wed, Aug 31, 2011 at 1:31 AM, robert wrote:
> > >
> > > running the job with --enable-parmesh doesn't change. I run only one
> > > mpi-job per node but it is still quit
Am Mittwoch, den 31.08.2011, 08:46 -0600 schrieb John Peterson:
> On Wed, Aug 31, 2011 at 1:31 AM, robert wrote:
> >
> > running the job with --enable-parmesh doesn't change. I run only one
> > mpi-job per node but it is still quite slow.
>
> You need to **reconfigure libmesh** with --enable-parm
On Wed, Aug 31, 2011 at 1:31 AM, robert wrote:
>
> running the job with --enable-parmesh doesn't change. I run only one
> mpi-job per node but it is still quite slow.
You need to **reconfigure libmesh** with --enable-parmesh and then recompile it.
--
John
--
Am Dienstag, den 30.08.2011, 21:19 +0200 schrieb robert:
> >
> > > It is possible to run 1, 2 or 4 processes per node. If I run 2 or 4
> > > processes I get:
> > > Error! ***Memory allocation failed for SetUpCoarseGraph: gdata.
> > > Requested size: 107754020 bytesError! ***Memory allocation fail
>
> > It is possible to run 1, 2 or 4 processes per node. If I run 2 or 4
> > processes I get:
> > Error! ***Memory allocation failed for SetUpCoarseGraph: gdata.
> > Requested size: 107754020 bytesError! ***Memory allocation failed for
> > SetUpCoarseGraph: gdata. Requested size: 107754020 byte
On Tue, Aug 30, 2011 at 12:34 PM, John Peterson wrote:
> On Tue, Aug 30, 2011 at 12:23 PM, robert wrote:
>>
>>> 32 nodes or 32 cores? I don't know the details of your cluster so it
>>> may be obvious, but make sure you aren't accidentally running too many
>>> MPI processes on a given node.
>>>
>
Am Dienstag, den 30.08.2011, 12:34 -0600 schrieb John Peterson:
> On Tue, Aug 30, 2011 at 12:23 PM, robert wrote:
> >
> >> 32 nodes or 32 cores? I don't know the details of your cluster so it
> >> may be obvious, but make sure you aren't accidentally running too many
> >> MPI processes on a given
On Tue, Aug 30, 2011 at 12:23 PM, robert wrote:
>
>> 32 nodes or 32 cores? I don't know the details of your cluster so it
>> may be obvious, but make sure you aren't accidentally running too many
>> MPI processes on a given node.
>>
> As far as I understood it it is:
>
> 1 node = 4cores
>
> 4GB/n
Am Dienstag, den 30.08.2011, 10:48 -0600 schrieb John Peterson:
> It will be extremely slow if it goes into swap.
>
> > Would this option just work with the existing code or do I have to
> > change to ParallelMesh?
>
> Should work with existing code. Hopefully.
>
> >
> > – SMP mode : 4 GB of
On Tue, Aug 30, 2011 at 10:36 AM, robert wrote:
> Am Dienstag, den 30.08.2011, 10:08 -0600 schrieb John Peterson:
>> On Tue, Aug 30, 2011 at 9:56 AM, robert wrote:
>> >
>> > The mesh.uniformly_refine(1) takes some minutes when I do it in serial
>> > on my PC. However, on the BlueGene/P it doesn't
Am Dienstag, den 30.08.2011, 10:08 -0600 schrieb John Peterson:
> On Tue, Aug 30, 2011 at 9:56 AM, robert wrote:
> >
> > The mesh.uniformly_refine(1) takes some minutes when I do it in serial
> > on my PC. However, on the BlueGene/P it doesn't come to an end (I
> > aborted after 15 min). Do I have
On Tue, Aug 30, 2011 at 9:56 AM, robert wrote:
>
> The mesh.uniformly_refine(1) takes some minutes when I do it in serial
> on my PC. However, on the BlueGene/P it doesn't come to an end (I
> aborted after 15 min). Do I have to prepare my mesh in a special way for
> use in parallel? One thing I ha
12 matches
Mail list logo
