[
https://issues.jboss.org/browse/FORGE-2670?page=com.atlassian.jira.plugin...
]
Daniel Platz commented on FORGE-2670:
-------------------------------------
Hi George,
I also would like to understand, so i am not giving up yet :-)
Maybe it is a combination of my system beeing slow due to some service but also a lot of
file-io done by forge.
Can you maybe on how much file-access you would expect during such a command-completion
event.
I am especially looking into DefaultFileOperations.fileExists as i was seen this a huge
part of the execution-time in jvisualmvm.
I have set an Exception-breakpoint to count the number of executions and for what files
like this:
{code:java}
java.nio.file.Files.write(java.nio.file.Paths.get("C:/_dump/out.txt"), (f +
"\n").getBytes(), java.nio.file.StandardOpenOption.APPEND);
return false;
{code}
What i get is attached file with a huge amount calls (~2500 file-system calls via
DefaultFileOperations.fileExists) during the command-completion. Is this expected/the same
on your system?
In case you do not oberserve this huge amounts of file-access, let me know if i can
provide you anything that might help further analysis. I really want to get the forge
console running! :-)
Command-completion is slow
--------------------------
Key: FORGE-2670
URL:
https://issues.jboss.org/browse/FORGE-2670
Project: Forge
Issue Type: Bug
Affects Versions: 3.2.3.Final
Environment: Windows 7 64-Bit; JDK 8 64-Bit
Intel Cor i7-4800MQ @ 2.7GHz
16 GB RAM
SSD
Reporter: Daniel Platz
Attachments: jforge.png, threaddumps.txt
When typing e.g. "comm" and hitting Tab, it takes approximately 2 seconds for
the command-completion to kick in and make suggestions/complete the command.
I have written about it already here:
https://developer.jboss.org/message/960679#960679
Not sure what best to provide to make analysis easier. I am also Ok with debugging it
myself if there maybe is a pointer in the right direction where to look into.
Regarding the questions in the forum post:
* I did not run any previous commands; it was this way from the beginning. I also deleted
the ~/.forge folder to start afresh. Same issue
* I used the forge console from within eclipse and from the cmd. Both the same.
* I am using the 3.2.3 Final version
I have attached a screenshot of the jvisualvm sampler. Steps i did:
1. Type "com"
2. Start sampler
3. Type "TAB"
4. Wait for command-completion
5. Stop sampler
It took approximately ~2 seconds for the command-compeltion to respond. it seems the
extensive checks like DefaultFileOperations.fileExists are a big part of it as it
accumlates to ~1 seconds which sound much.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)