Why does eclipse have more than 100 filehandles to the same file ? [message #28596] |
Wed, 07 May 2003 08:58  |
Eclipse User |
|
|
|
In our company we all have the eclipse metadata catalog on our homedrive,
which is located on a windows fileserver.
The problem is that eclipse has a more than 100 open filehandles on
.plugins\org.eclipse.core.resources\.history\.index , which is bringing our
server to a crawl.
I would like to know if this is a bug, has anyone else seen this ?
/Ruben Hesselb
|
|
|
Re: Why does eclipse have more than 100 filehandles to the same file ? [message #28634 is a reply to message #28596] |
Wed, 07 May 2003 11:40   |
Eclipse User |
|
|
|
Originally posted by: jed_anderson.us.ibm.com
Ruben,
Whether or not anyone else has seen this, I suggest you write up a bug
report for this. This may be by design, but I doubt it. :)
Assign it to platform core, and make sure to fill in all of the details
of your configuration (Eclipse version, VM, etc), and how you noticed so
many open handles.
Thanks!
jkca
Ruben Hesselbæk wrote:
> In our company we all have the eclipse metadata catalog on our homedrive,
> which is located on a windows fileserver.
> The problem is that eclipse has a more than 100 open filehandles on
> .plugins\org.eclipse.core.resources\.history\.index , which is bringing our
> server to a crawl.
>
> I would like to know if this is a bug, has anyone else seen this ?
>
> /Ruben Hesselbæk
>
>
|
|
|
Re: Why does eclipse have more than 100 filehandles to the same file ? [message #29633 is a reply to message #28596] |
Fri, 09 May 2003 06:08  |
Eclipse User |
|
|
|
Originally posted by: genadyb.inter.net.il
What I have noticed is that eclipse is terribly slow on network drives.
It can be a reason.
I did a simple test of compiling (saving) one file, in a project that
has only two files.
Now, I have used a file access monitor program, and it shows that
compiling the file results in about ~10,000 OS-level file access operations:
Here is the list (remember - it is a result of compiling just one! file):
8526 C:\jdk-1.4.1\jre\lib\rt.jar
416 C:\jdk-1.4.1\jre\lib\jsse.jar
177 C:\jdk-1.4.1\jre\lib\ext\localedata.jar
99 C:\jdk-1.4.1\jre\lib\sunrsasign.jar
78 C:\jdk-1.4.1\jre\lib\ext\sunjce_provider.jar
68 ...\workspace\rmi-test4\RemoteClass.java
61 ...\workspace\.metadata\.plugins\org.eclipse.jdt.core\129181 6999.index
54 ...\workspace\rmi-test4\
53 C:\jdk-1.4.1\jre\lib\jce.jar
46
....\workspace\.metadata\.plugins\org.eclipse.jdt.core\12918 16999.indexTempVA
30 C:\
24 ...\workspace\
24 C:\eclipse\
20
....\workspace\.metadata\.plugins\org.eclipse.core.resources \.history\.index.log
20
....\workspace\.metadata\.plugins\org.eclipse.core.resources \.history\.index
18 ...\workspace\.metadata\.plugins\
18 ...\workspace\.metadata\
13 ...\workspace\rmi-test4\RemoteClass.class
12 ...\workspace\rmi-test4
10
....\workspace\.metadata\.plugins\org.eclipse.core.resources \.history\5c
9 ...\workspace\.metadata\.plugins\org.eclipse.jdt.core\
9
...\workspace\.metadata\.plugins\org.eclipse.core.resources\ .history\5c\00b43ff40282001716c5bbf66f15be0b
9 ...\workspace\.metadata\.plugins\org.eclipse.core.resources\ .history\
9 ...\workspace\.metadata\.plugins\org.eclipse.core.resources\
6 C:\jdk-1.4.1\jre\lib\
6 C:\jdk-1.4.1\jre\
6 C:\jdk-1.4.1\
6
....\workspace\.metadata\.plugins\org.eclipse.jdt.core\saved IndexNames.txt
6
....\workspace\.metadata\.plugins\org.eclipse.core.resources \.history\5c\
5 C:\jdk-1.4.1\jre\lib\charsets.jar
3 C:\jdk-1.4.1\jre\lib\ext\ldapsec.jar
3 C:\jdk-1.4.1\jre\lib\ext\dnsns.jar
3 ...\workspace\rmi-test4\MyRemote.class
3
....\workspace\.metadata\.plugins\org.eclipse.core.resources \.projects\rmi-test4\org.eclipse.jdt.core
2 C:\Recycler\NProtect\00011130.IND
2 C:\Recycler\NProtect\00011126.LOG
1
....\workspace\.metadata\.plugins\org.eclipse.core.resources \.projects\rmi-test4\org.eclipse.jdt.core\state.dat
Genady
Ruben Hesselbæk wrote:
> In our company we all have the eclipse metadata catalog on our homedrive,
> which is located on a windows fileserver.
> The problem is that eclipse has a more than 100 open filehandles on
> .plugins\org.eclipse.core.resources\.history\.index , which is bringing our
> server to a crawl.
>
> I would like to know if this is a bug, has anyone else seen this ?
>
> /Ruben Hesselbæk
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.02600 seconds