warn message in log summary

2007-11-26 Thread Lisandro Dalcin
On 11/24/07, Barry Smith bsmith at mcs.anl.gov wrote: To minor question about this message: * What means 'to rapid calls'? Is it a typo? Should be 'too rapid calls' ? Yup * Perhaps a newline could be added after the warn mesage? Yup Then I'll fix the formating. I hate this message

warn message in log summary

2007-11-26 Thread Richard Tran Mills
Lisandro, Unfortunately, I see the same negative timings problem on the Cray XT3/4 systems when I configure PETSc to use MPI_Wtime() for all its timings. So that doesn't necessarily fix anything... --Richard Lisandro Dalcin wrote: Perhaps PETSc should use MPI_Wtime as default timer. If a

warn message in log summary

2007-11-26 Thread Lisandro Dalcin
On 11/26/07, Richard Tran Mills rmills at ornl.gov wrote: Lisandro, Unfortunately, I see the same negative timings problem on the Cray XT3/4 systems when I configure PETSc to use MPI_Wtime() for all its timings. So that doesn't necessarily fix anything... Could you please try the small

warn message in log summary

2007-11-26 Thread Lisandro Dalcin
I even get consistent time deltas using 'gettimeofday' on my box!! Perhaps PETSc has some bug somewere?? What do you think?? On 11/26/07, Richard Tran Mills rmills at ornl.gov wrote: Lisandro, Unfortunately, I see the same negative timings problem on the Cray XT3/4 systems when I configure

warn message in log summary

2007-11-26 Thread Barry Smith
I've looked long and hard for a PETSc bug that would cause this problem. No luck. It seems to happen mostly (only?) on certain machines. Barry On Nov 26, 2007, at 11:03 AM, Lisandro Dalcin wrote: I even get consistent time deltas using 'gettimeofday' on my box!! Perhaps PETSc has

warn message in log summary

2007-11-26 Thread Lisandro Dalcin
On 11/26/07, Barry Smith bsmith at mcs.anl.gov wrote: I've looked long and hard for a PETSc bug that would cause this problem. No luck. It seems to happen mostly (only?) on certain machines. Ups! I've found a possilbe source of the problem, at least for my case! Those negative times I got

warn message in log summary

2007-11-26 Thread Matthew Knepley
On Nov 26, 2007 4:19 PM, Lisandro Dalcin dalcinl at gmail.com wrote: On 11/26/07, Barry Smith bsmith at mcs.anl.gov wrote: I've looked long and hard for a PETSc bug that would cause this problem. No luck. It seems to happen mostly (only?) on certain machines. Ups! I've found a possilbe

warn message in log summary

2007-11-26 Thread Matthew Knepley
That seems fine. Matt On Nov 26, 2007 4:56 PM, Lisandro Dalcin dalcinl at gmail.com wrote: On 11/26/07, Matthew Knepley knepley at gmail.com wrote: On Nov 26, 2007 4:19 PM, Lisandro Dalcin dalcinl at gmail.com After surfing the code and hacked PetscLogPrintSummary(), I added a