From 88db9c010c999f4fc3e287d746e14577245c737c Mon Sep 17 00:00:00 2001 From: Wolfgang Bangerth Date: Sun, 17 Mar 2013 16:02:54 +0000 Subject: [PATCH] Mention PETSc's optimized mode. git-svn-id: https://svn.dealii.org/trunk@28922 0785d39b-7218-0410-832d-ea1e28bc413d --- deal.II/doc/external-libs/petsc.html | 20 ++++++++++++++++++-- 1 file changed, 18 insertions(+), 2 deletions(-) diff --git a/deal.II/doc/external-libs/petsc.html b/deal.II/doc/external-libs/petsc.html index c9e8708c9f..ab786ce663 100644 --- a/deal.II/doc/external-libs/petsc.html +++ b/deal.II/doc/external-libs/petsc.html @@ -5,7 +5,7 @@ The deal.II Readme on interfacing to PETSc - + @@ -47,7 +47,9 @@ PETSc usually requires you to set the environment variables PETSC_DIR and PETSC_ARCH to a path to PETSc and denoting the architecture for which PETSc is - compiled. If these environment variables are set, then + compiled (a string you can choose however you like, it is simply + intended to identify one of possibly several different PETSc + installations). If these environment variables are set, then deal.II will pick them up during configuration, and store them. It will then also recognize that PETSc shall be used, and enable the wrapper classes. @@ -129,6 +131,20 @@

+

+ By default, PETSc is compiled in "debug mode". You can switch this to + "optimized mode" by adding the command line parameter +

+
+	--with-debugging=0
+      
+ to the call of ./config/configure.py above. In some cases, + this has made linear solvers run up to 30% faster. As with choosing + between deal.II's debug and optimized modes, you + should only use optimized PETSc builds once you have tested that your + program runs well in debug mode. +

+
-- 2.39.5