summaryrefslogtreecommitdiffstats
path: root/src/doxygen.cpp
diff options
context:
space:
mode:
authorCharles.Lee <cheoljoo@gmail.com>2018-08-27 03:14:55 (GMT)
committerCharles.Lee <cheoljoo@gmail.com>2018-08-27 03:14:55 (GMT)
commit1a9bb0614362217143d8e01779d8ac9b336b96f4 (patch)
tree36ec658ef5ab1530ea8d4a18fb6f7b7c8cafe656 /src/doxygen.cpp
parent94a52469b177703d3e0d94bed6c4a48bddba18cb (diff)
downloadDoxygen-1a9bb0614362217143d8e01779d8ac9b336b96f4.zip
Doxygen-1a9bb0614362217143d8e01779d8ac9b336b96f4.tar.gz
Doxygen-1a9bb0614362217143d8e01779d8ac9b336b96f4.tar.bz2
Imporvement of performance : Reduce the Java running count
# What is it - #6465 is the first reqeust. So I followed up the albert advice. - in case of debug you use printf statements, I think that here there better options would be - create an -d flag (e.g. -d plantuml) that gives the information, so no need for using the configuration option - Follow up : create -d plantuml [debug.h, debug.cpp] - usage of printf - printf should not be used,all output is steered over calls to routines as defined in message.cpp, - Follow up : use Debug::Print(Debug::Plantuml, ... and msg() - usage of std::string / std::map - in doxygen the string manipulation is. mostly, done by means of Qt classes (e.g. classes QCString, QString). For consistency these classes should be used. - map manipulation is also done by means of Qt classes (dictionary and list classes) - Follow up : use QDict QList QCString [plantuml.h, plantuml.cpp] - dirent / opendir /readdir - when browsing through directories the routines line readFileOrDirectory should probably be used or the techniques used in this routine - Follow up : I will follow when I try to reduce redundancy of creating plantuml image. - Run java minimally - Test Case : 4 plantuml - Original Run without PLANTUML_RUN_JAVA_ONCE - 8.2 sec = 4 times * ( 1.6(java vm) + 0.1 * 1(load multiple file) + process each plantuml (0.35) *1 ) <- prediction - New with PLANTUML_RUN_JAVA_ONCE - 3.499 sec = 1.6(java vm) + 0.1 * 4(load multiple file) + process each plantuml (0.35) *4 <- prediction - Creating Java Virtual Machine has a big portion. - Result - Improving Performance : 8.2 -> 3.499 (in case of 4 plantuml) # Configuration - add configuration value in Doxyfile - PLANTUML_RUN_JAVA_ONCE = YES # Debugging - doxygen -d plantuml - doxygen -d time -d plantuml # Tested with following options - source code of 3 plantuml - PLANTUML_RUN_JAVA_ONCE = YES or NO - DOT_IMAGE_FORMAT = png or svg - DOT_CLEANUP = YES or NO - -d plantuml
Diffstat (limited to 'src/doxygen.cpp')
-rw-r--r--src/doxygen.cpp8
1 files changed, 8 insertions, 0 deletions
diff --git a/src/doxygen.cpp b/src/doxygen.cpp
index bf93a9b..b33ae49 100644
--- a/src/doxygen.cpp
+++ b/src/doxygen.cpp
@@ -103,6 +103,7 @@
#include "settings.h"
#include "context.h"
#include "fileparser.h"
+#include "plantuml.h"
// provided by the generated file resources.cpp
extern void initResources();
@@ -11707,6 +11708,13 @@ void generateOutput()
g_s.end();
}
+ if (Config_getBool(PLANTUML_RUN_JAVA_ONCE))
+ {
+ g_s.begin("Running plantuml with JAVA...\n");
+ PlantumlManager::instance()->run();
+ g_s.end();
+ }
+
if (Config_getBool(HAVE_DOT))
{
g_s.begin("Running dot...\n");