优化大型基地的OpenGrok
我在这里有一个服务器实例,安装了4个核心,32 GB RAM和UBUNTU 20.04.3 LTS。在这台计算机上,有一个opengrok-instance作为Docker容器运行。
在Docker容器内部,它使用采用optopenjdk:
OpenJDK Runtime Environment AdoptOpenJDK-11.0.11+9 (build 11.0.11+9)
Eclipse OpenJ9 VM AdoptOpenJDK-11.0.11+9 (build openj9-0.26.0, JRE 11 Linux amd64-64-Bit Compressed References 20210421_975 (JIT enabled, AOT enabled)
OpenJ9 - b4cc246d9
OMR - 162e6f729
JCL - 7796c80419 based on jdk-11.0.11+9)
OpenGrok-Indexer扫描为320 GB的代码库,大量为21小时。
我被认为是的是,我禁用了花费更少的时间的历史选择。如果设置了历史记录,是否有可能减少这段时间。
这是我的索引命令:
OpenGrok-Indexer -j = -djava.util.util.logging.manager = org.apache.juli.juli.classloaderlogmanager -j = -djava.util.util.util.logging.config.config.file.file =/usr/share =/usr/share =/usr/share =/usr/share =/usr/share /tomcat10/conf/logging.properties -j = -xx:-usegcoverheadlimit -j = -xmx30g -j = -XMS30G -J = -Server -a/var/var/opengrok/dist/lib/lib/opengrok/opengrok/opengrok.jar--r--r/--r/-r/r/r/ var/opengrok/etc/read -only.xml -m 256 -c/usr/bin/ctags -s/var/opengrok/src/src/-d/var/opengrok/data -remote -h -p -s-s-s-s-s-p -s-s-s-p -s-s-s- g -w/var/opengrok/etc/configuration.xml -progress -v -o on -t 3 -assigntags -search -remote -i *.so -i -i *.o -i *.o -i -i *.A- i *.class -i *.jar -i *.apk -i *.tar -i *.bz2 -i *.gz -i *.obj -i *.zip“
谢谢您的帮助进步
i have a server instance here with 4 Cores and 32 GB RAM and Ubuntu 20.04.3 LTS installed. On this machine there is an opengrok-instance running as docker container.
Inside of the docker container it uses AdoptOpenJDK:
OpenJDK Runtime Environment AdoptOpenJDK-11.0.11+9 (build 11.0.11+9)
Eclipse OpenJ9 VM AdoptOpenJDK-11.0.11+9 (build openj9-0.26.0, JRE 11 Linux amd64-64-Bit Compressed References 20210421_975 (JIT enabled, AOT enabled)
OpenJ9 - b4cc246d9
OMR - 162e6f729
JCL - 7796c80419 based on jdk-11.0.11+9)
The code-base that the opengrok-indexer scans is 320 GB big and tooks 21 hours.
What i am figured is out was, that i've am disable the history-option it tooks lesser time. Is there a possibility to reduce this time, if the history-flag is set.
Here are my index-command:
opengrok-indexer -J=-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -J=-Djava.util.logging.config.file=/usr/share/tomcat10/conf/logging.properties -J=-XX:-UseGCOverheadLimit -J=-Xmx30G -J=-Xms30G -J=-server -a /var/opengrok/dist/lib/opengrok.jar -- -R /var/opengrok/etc/read-only.xml -m 256 -c /usr/bin/ctags -s /var/opengrok/src/ -d /var/opengrok/data --remote on -H -P -S -G -W /var/opengrok/etc/configuration.xml --progress -v -O on -T 3 --assignTags --search --remote on -i *.so -i *.o -i *.a -i *.class -i *.jar -i *.apk -i *.tar -i *.bz2 -i *.gz -i *.obj -i *.zip"
Thank you for your help in advance.
Kind Regards
Siegfried
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
您应该尝试使用以下选项来增加线程数:
也要查看“重命名史”选项。理论上“关闭”是默认选项,但这对索引时间产生了巨大影响,因此值得检查:
You should try to increase the number of threads using the following options:
Take a look at the "renamedHistory" option too. Theoretically "off" is the default option but this has a huge impact on the index time, so it's worth the check: