Eclipse Community Forums: ServerTools (WTP) » Bad performance of XML Schema Editor

Home » Language IDEs » ServerTools (WTP) » Bad performance of XML Schema Editor

Bad performance of XML Schema Editor [message #115933]

Mon, 04 July 2005 16:28

Eclipse User

Hello,

is there any reason for slow performance of Graph page of XML Schema Editor ?
Anytime i click on graph page (or when i expand some subitem in graph), the
CPU is used at 90% for around a 30-60 secs by Eclipse (and Eclipse looks like
freezed). This makes graphical XML Schema editor unusable.

Eclipse 3.1 (built from source on Gentoo Linux), WTP 0.7M5.

Frantisek Augusztin

Re: Bad performance of XML Schema Editor [message #115958 is a reply to message #115933]

Mon, 04 July 2005 15:25

Eclipse User

Hi Frantisek,

Doesn't sound like the schema editor is usable in your scenario. Please
open a bug against the wsd.xsd component. It will be helpful if you can
attach a schema file that reproduces the problem as well. Also, please be
sure to include the version of your OS, JRE, Eclipse, and WTP as well. (I
saw that you did include the versions of Eclipse and WTP in your post,
thanks!)

Lawrence

Re: Bad performance of XML Schema Editor [message #115984 is a reply to message #115958]

Mon, 04 July 2005 17:51

Eclipse User

> Doesn't sound like the schema editor is usable in your scenario. Please
> open a bug against the wsd.xsd component. It will be helpful if you can
> attach a schema file that reproduces the problem as well. Also, please be
> sure to include the version of your OS, JRE, Eclipse, and WTP as well. (I
> saw that you did include the versions of Eclipse and WTP in your post,
> thanks!)

It looks like that i found out the reason why it worked so badly. That schema
(unfortunaly not public) is 700kB big ! This maybe used all memory of Eclipse
and other schemas performed so badly because this schema used all the memory.
Now when i tried to open schema it even run out of memory. It's a unusual schema,
but such bad performance is realy bad.

It look that this is not really a bug (700kB schema is very rare). If you want
i can open a bug report, but i cannot provide the schema.

Frantisek Augusztin

Re: Bad performance of XML Schema Editor [message #116059 is a reply to message #115984]

Mon, 04 July 2005 18:06

Eclipse User

Hi Frantisek,

I've noticed that as well (it's slow with large XSDs) however, I think I
also noticed that things went better when I was getting rid of global
complex types...

If you have a large XSD and watch some CPU monitor, you will notice two
consecutive spikes every 20 secs or so.

Hope this helps.

A.

Re: Bad performance of XML Schema Editor [message #116082 is a reply to message #116059]

Mon, 04 July 2005 18:31

Eclipse User

Originally posted by: bob.objfac.com

What does "large" mean?

Bob

Alain Pannetier wrote:
> Hi Frantisek,
>
> I've noticed that as well (it's slow with large XSDs) however, I think I
> also noticed that things went better when I was getting rid of global
> complex types...
>
> If you have a large XSD and watch some CPU monitor, you will notice two
> consecutive spikes every 20 secs or so.
>
> Hope this helps.
>
> A.
>

Re: Bad performance of XML Schema Editor [message #116555 is a reply to message #116082]

Wed, 06 July 2005 04:56

Eclipse User

Hello Bob,

3000 lines. An XSD for Tomcat 5.5 server.xml conf file.
That's not *very* 'large' indeed.

If I've got a minute, I'll do some basic profiling on the plugin...

Cheers,

Alain

Re: Bad performance of XML Schema Editor [message #116755 is a reply to message #115933]

Wed, 06 July 2005 11:48

Eclipse User

Originally posted by: chabert.fimasys.fr

Hello,

I also encounter problems with Schema containing many complexType nodes,
even if the file is not big. Eclipse freeze when I try to format my
Schema document source. FInally, my document is formatted, but it took
15-20 minutes.
I already opened a bug about it:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=102822

Regards,
Sylvain

Frantisek Augusztin wrote:
> Hello,
>
> is there any reason for slow performance of Graph page of XML Schema Editor ?
> Anytime i click on graph page (or when i expand some subitem in graph), the
> CPU is used at 90% for around a 30-60 secs by Eclipse (and Eclipse looks like
> freezed). This makes graphical XML Schema editor unusable.
>
> Eclipse 3.1 (built from source on Gentoo Linux), WTP 0.7M5.
>
> Frantisek Augusztin

Re: Bad performance of XML Schema Editor [message #117033 is a reply to message #116755]

Wed, 06 July 2005 18:01

Eclipse User

Originally posted by: nospam.ronald_vankuijk_net.remove

Sylvain Chabert wrote:
>
> Hello,
>
> I also encounter problems with Schema containing many complexType nodes,
> even if the file is not big. Eclipse freeze when I try to format my
> Schema document source. FInally, my document is formatted, but it took
> 15-20 minutes.
> I already opened a bug about it:
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=102822
>
> Regards,
> Sylvain
>
> Frantisek Augusztin wrote:
>> Hello,
>>
>> is there any reason for slow performance of Graph page of XML Schema
>> Editor ?
>> Anytime i click on graph page (or when i expand some subitem in
>> graph), the
>> CPU is used at 90% for around a 30-60 secs by Eclipse (and Eclipse
>> looks like
>> freezed). This makes graphical XML Schema editor unusable.
>>
>> Eclipse 3.1 (built from source on Gentoo Linux), WTP 0.7M5.
>>
>> Frantisek Augusztin

Try validating an xml file against this schema outside eclipse with just
xalan. That probably fails to (it does for me) seems more likely a
xalan issue than an eclipse issue. Did you get an OOM error? I had 45MB
of byte[] for a 300k xsd dictonary used (imported) by a 20k xsd

Ronald

Re: Bad performance of XML Schema Editor [message #118849 is a reply to message #116555]

Sat, 09 July 2005 12:05

Eclipse User

Hello,

So, I eventually got around profiling the workbench with my XML schema
open.
It actually took me a while because I had to do my own porting of eclipse
profiler plugin (Konstantin Scheglov's) to Eclipse 3.1.

First of all I want to say that if I use a normal, simple XML schema,
everything works fine.
That is, as soon as the XSD is loaded and validated, the CPU counters
freeze.

On the other hand, if I load my XSD (a valid one, if I'm to believe the
validator and XMLS[lop]py), then things start to go wrong.
First of all, the CPU keeps working even if I only loaded the file in the
editor. I don't even edit it.
Here are a few conclusions from eclipse profiler
- Only one worker thread is to blame.
- This thread execute in continuation the
org.eclipse.wst.sse.ui.internal.reconcile.DirtyRegionProcess or#run

If I follow the path of the most CPU hungry calls I drill down as follows.
I've added the number of invocations counted by Eclipse Profiler so that
one understands where the 'gap' lies, percentage are CPU% for that thread.

100% 1 invocation -
org.eclipse.wst.sse.ui.internal.reconcile.DirtyRegionProcess or#run
100% 1 invocation -
org.eclipse.wst.sse.ui.internal.reconcile.StructuredRgionPro cess.process
87% 66 invocations -
org.eclipse.wst.sse.ui.internal.reconcile.AbstractStructured TextReconcilingStrategy#reconcile
87% 66 invocations -
org.eclipse.wst.sse.ui.internal.validation.ReconcileStepForM arkup#reconcileModel
66% 66 invocations -
org.eclipse.wst.sse.ui.internal.validation.ReconcileStepForM arkup#getStructuredDocumentRegions
65% 236783 invocations -
org.eclipse.wst.xml.core.internal.document.DOMModelIml#getIn dexedRegion

So I guess there is something wrong in
ReconcileStepForMarkup#getStructuredDocumentRegions that results in never
returning.

So I got into the src code and I found this bit.
I don't know the context but I wonder when you get out of this loop.
Could that be it ?

while (sdRegion != null
&& !sdRegion.isDeleted()
&& xmlNode != null
&& sdRegion.getEndOffset() <= xmlNode.getEndOffset()) {
if (!sdRegion.isDeleted())
regions.add(sdRegion);
sdRegion = sdRegion.getNext();
xmlNode = getXMLNode(sdRegion);
}

Hope this helps to make this very nice XSD editor more usable ;-)

If you need my XSD or assistance with the Eclipse Profiler plugin
(it's very powerful but, having been developed for Eclipse version 2, it's
aging a bit), please fee free to send me a mail at
alain dot m dot pannetier at atosorigin dot com

Alain Pannetier

Previous Topic:	Odd behavior when publishing web project with deps
Next Topic:	EJB deployment with WTP

Goto Forum:

-=] Back to Top [=-

Current Time: Wed May 07 08:49:38 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter