This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 198514 - XML/XSL completion too slow
Summary: XML/XSL completion too slow
Status: RESOLVED FIXED
Alias: None
Product: xml
Classification: Unclassified
Component: XSL (show other bugs)
Version: 7.0.1
Hardware: PC Windows XP
: P2 normal (vote)
Assignee: Svata Dedic
URL:
Keywords: PERFORMANCE
Depends on:
Blocks:
 
Reported: 2011-05-11 12:40 UTC by Peter Nabbefeld
Modified: 2011-10-17 12:21 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 178059

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Nabbefeld 2011-05-11 12:40:55 UTC 
All my exception reports have been added to bug #197270, so I've added the same exception report (#178059) here.

Bug #197270 originally was a report about CSS slowness, but only two of more than 200 were related to CSS. As all my XSL slowness reports have been added there, too, most reports are probably about XSL (didin't check, though).

It's nearly impossible for me to use code completion, as it sometimes needs even a minute or more. :-(
Comment 1 Svata Dedic 2011-09-22 07:30:12 UTC 
Please check whether during the observed slowdown of completion the IDE tries to access the Internet; in particular whether it makes requests to www.w3.org.
Comment 2 Peter Nabbefeld 2011-09-22 07:57:10 UTC 
(In reply to comment #1)
> Please check whether during the observed slowdown of completion the IDE tries
> to access the Internet; in particular whether it makes requests to www.w3.org.

This is probably just a duplicate of bug #197467, the difference being about slowness reports.

One issue is: I cannot use schema constrained tags like for xslt (seems to work better when it is "pure").

The second issue is on working with non-constrained documents, i.e. working with my own markup without any schema. This still needs several minutes, probably there's some update of schema on every non-recognized tag, though namespace is not the same.

Seems like tags are transferred into a memory-based model without their namespace bindings. If there's any namespace in the model, all the models are probably searched for the non-recognized tag. Even worse, some used namespaces are not even locally available, so searching for their schemas will always fail.
Comment 3 Svata Dedic 2011-10-03 14:51:54 UTC 
Most of the slowness should be fixed - if you survive the 1st download of XSDs from w3c :)

I am trying to include well-known schemas into the distribution, so the completion and other features can use local resources instead of downloading them, but need to get legal OK (different licenses) on that.
Comment 4 Svata Dedic 2011-10-17 12:21:33 UTC 
Fixed; schemas included in jet-main #31a8722f9944