[Paraview] [Non-DoD Source] Re: Using 64 or more cores on a single node when running client/server (UNCLASSIFIED)

[Su, Simon M CIV USARMY RDECOM ARL (US)]

CLASSIFICATION: UNCLASSIFIED

thank you Utkarsh.  that's the confirmation that we are looking. We will
test the MPI.

thanks
-simon

-----Original Message-----
From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Utkarsh
Ayachit
Sent: Wednesday, September 13, 2017 12:12 PM
To: Patrick Begou <Patrick.Begou at legi.grenoble-inp.fr>
Cc: paraview at paraview.org
Subject: [Non-DoD Source] Re: [Paraview] Using 64 or more cores on a single
node when running client/server

All active links contained in this email were disabled.  Please verify the
identity of the sender, and confirm the authenticity of all links contained
within the message prior to copying and pasting the address to a Web
browser.  




----

> It should be related to your mpi environment: may be oversubscribing 
> (more than one mpi process by core) is not the default behavior.

I am tempted to second that. There's nothing in ParaView that checks how
many cores your node has, as a result if there's a cap, it's coming from the
MPI implementation itself.
_______________________________________________
Powered by Caution-www.kitware.com

Visit other Kitware open-source projects at
Caution-http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at:
Caution-http://paraview.org/Wiki/ParaView

Search the list archives at: Caution-http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
Caution-http://public.kitware.com/mailman/listinfo/paraview


CLASSIFICATION: UNCLASSIFIED
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5567 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20170913/ee29ed50/attachment.bin>