[Paraview-developers] [EXTERNAL] Re: problems with >64 pvservers

[burlen]

Sorry to chime in so late here, just wanted to mention that mem 
inspector, for efficiency, makes no server queries if it is not visible. 
It's completely disabled by un-checking the mem inspector element in the 
view menu.

Glad your issue was resolved
Burlen

On 02/12/2013 11:24 PM, Biddiscombe, John A. wrote:
> Alan
>
> I have upgraded to the latest 3.98.1 from master and the hang is fixed. I tested up to 512 processes and all seems normal.
>
> Thanks
>
> JB
>
> -----Original Message-----
> From: Scott, W Alan [mailto:wascott at sandia.gov]
> Sent: 12 February 2013 19:00
> To: Utkarsh Ayachit; Biddiscombe, John A.
> Cc: paraview-developers at paraview.org
> Subject: RE: [EXTERNAL] Re: [Paraview-developers] problems with >64 pvservers
>
> One other idea - There is a known hang in ParaView (fixed in 3.98.1, and master about 1.5 weeks ago) remote server, where a threshold is exceeded.  This was in the code for the Progress Bar, bottom of ParaView.  This limit had been at over 1024 processes, but was reduced to  64 processes, as we were trying to fix other issues.   To test, either update, or reduce your pvserver count to under 64 (doing this from memory!).  See this bug group for details: http://paraview.org/Bug/view.php?id=13839 (the child of interest) and http://paraview.org/Bug/view.php?id=13831 (parent bug).
>
> With regards to 3.98.1, and current master, as stated by Utkarsh, I tested at 256 cores/processes/pvservers, and went to scale with Wavelet.  Worked like a champ.
>
> Alan
>
> -----Original Message-----
> From: paraview-developers-bounces at paraview.org [mailto:paraview-developers-bounces at paraview.org] On Behalf Of Utkarsh Ayachit
> Sent: Tuesday, February 12, 2013 6:49 AM
> To: Biddiscombe, John A.
> Cc: paraview-developers at paraview.org
> Subject: [EXTERNAL] Re: [Paraview-developers] problems with >64 pvservers
>
>> I'm using pv3.98 master from about 2 weeks ago and can do a pull - but
>> I doubt it'll make a difference (I had this problem before and pulled
>> in the hope it'd be fixed). I'm currently suspecting the new memory
>> inspector as a possible cause of hang around startup - but this is
>> based on no evidence, so take it with a pinch of salt.
> I recently noticed that there is some dns name lookup so something of that sort happening at startup (for the memory inspector) that can "lock" on machines with DNS issues. Try commenting out host name related lookup in SystemInformation.cxx (I can send more details when I get to work, if needed). Is that a possibility in your setup? I believe Alan did a 256 node test before we tagged the release so >64 pvserver should not be an issue.
> _______________________________________________
> Paraview-developers mailing list
> Paraview-developers at paraview.org
> http://public.kitware.com/mailman/listinfo/paraview-developers
>
>
> _______________________________________________
> Paraview-developers mailing list
> Paraview-developers at paraview.org
> http://public.kitware.com/mailman/listinfo/paraview-developers