What makes Domino Designer slow when developing xPages? - some observations ...

David Marko  19 September 2011 08:48:12
We have been working on some real-life projects using xPages recently and we have done some observations on Domino Designer slowness of xPages editor. DDE is very slow for xPages development in general (all the 'building workspace' delays :-( ) but we found out that sometimes its much worse ...

I would like to mention two cases, maybe they can help you as well ...
a) you have the view datasource on xPage pointing to database and view with many, many documents.

- seems like the Domino is maintaining and refreshing the connection to view in xPages editor and when view is slow to refresh then the entire xPage is very slow in dev mode. For some huge views we encountered extreme slowness of xPages editor. Type frequency into source editor was one char per 10 second ... sometimes even worse. By simply removing view datasource solves the problem. But you probably need the datasource ... so we changed the view datasource's database and view properties to computed ones and moved code to our java code(we use managed beans aka singleton pattern helpers). Since that Domino cant reach the view in development mode so slowness disappeared.

b) you have JavaScript or CSS resources on xPages pointing to external files

- we were developing xPages application for mobiles using JQuery Mobile library. We have added some CSS and JS resources on xPage and  linked  them directly to CDN. In HTML you will get something like:

... script src="http://code.jquery.com/mobile/1.0b3/jquery.mobile-1.0b3.min.js" ...

But having this in xPage's resources causes extreme slowness when working in source code editor. Cant understand why it is, when we removed this resources, everything was fine. Then we downloaded the all linked libraries, put these into database and made xPages resources pointed to these local files ... and speed was still fine. So the moral here is this: don't use external resources ...

and both observations were made on Domino Designer 8.5.2FP2 and 8.5.3CD5 with the same results.

I still have many, many questions regarding the overall speed. Just mentioning one: Why is Designer refreshing/building workspace(slow process) every time I update CSS file or JavaScript library file? These are totally independent on xPage or other code ... these are just simple text files. So why I have to wait 10 seconds to see CSS update in browser waiting on 'building workspace' process to finish. :-( Do some CSS refinements requiring 30 CSS file updates in hour and this entire slowness makes you crazy ...

Image:What makes Domino Designer slow when developing xPages? - some observations ...
Comments

1Michael Ruhnau  19.09.2011 15:14:17  What makes Domino Designer slow when developing xPages? - some observations ...

Thanks for sharing these insights.

I usually try to use a template with no or only a few documents for development. I think this would also avoid the first issue you are mentioning.

2Nathan T. Freeman  19.09.2011 15:54:57  What makes Domino Designer slow when developing xPages? - some observations ...

There are a number of issues related to this topic that I am bound by non-disclosure on, and so cannot discuss. However, one part was discovered independently, and so I can share it here...

"But having this in xPage's resources causes extreme slowness when working in source code editor. Cant understand why it is,"

A non-obvious behavior of the XPages editor is that ALL hrefs attempt to be resolved by the editor itself during many events. This can include EVERY KEYSTROKE in the source tab, when you're adding new tags or new href references to the editor. So as you type, with each keypress, the editor is behind the scenes attempting to resolve every external reference via http requests. It's not even smart enough to cache the results.

I have hunted in vain for a way to suppress this behavior. The best option I have found so far is simply this...

If you intend to work solely in the source editor, go to the Package Explorer and open the .xsp file using the standard Eclipse XML editor instead of the XPages editor. You'll still get syntax highlighting and auto-closure of your tags, but without all the slowdowns people experience.

You'll lose the ability to drag/drop from the palette, but most developers I know who live in the Source tab don't really use the palette anyway.

3David Marko  19.09.2011 16:22:11  What makes Domino Designer slow when developing xPages? - some observations ...

@Nathan T. Freeman

You are right, the XML editor is much faster as its not bound to xPages. But what worse is that there is no property tab for xPages tags and without completion feature you must have everything in yout head. BTW. why there is no xml code completion available in source code editor? Standard XML editor in pure eclise uses DTD info for XML completion, so basicly one doesnt need visual tools. There are even no html tags available for ctrl+space, also available in common HTML editor in pure Eclipse.

4Nathan T. Freeman  19.09.2011 16:32:34  What makes Domino Designer slow when developing xPages? - some observations ...

Because there is no schema for XSP. And honestly, given it's nature, there CANNOT be a generalized schema for XSP. There can only be a schema for a given XSP Application. It would need to be generated programmatically based on the libraries and custom controls in use by that particular app.

5Alec Paul  03.10.2016 22:42:59  What makes Domino Designer slow when developing xPages? - some observations ...

I agree with Nathan, thanks for the tip, working with the Eclipse XML is a little faster or" you can live with it" but still slow, seems that you better watch you type or you will mess up the entire XML bracketing and end up trouble shooting line by line or looking into the OUTLINE which I found very helpful like development into Dreamweaver ... which is what the XSP page needs to become more like if IBM want to compete with it..

Nevertheless, I really like XSP pages and how domino build us a way to do that. but big big learning curve on how to pass information back and forth and SSJS is that key to all. whole different animal.

Trying to find a faster editor still for the xsp source..with the domino data or ssjs together.. but for now using your suggestion with eclipse xml editor. any technique you can add will be GREATLY appreciated

6Alec Paul  04.10.2016 19:13:09  What makes Domino Designer slow when developing xPages? - some observations ...

OK an update, I found out few glitches and it helped speed up and notes preforms like its expected..

for some weird reason, it was slow everywhere, so I deleted the bookmark.nsf and could not believe it, it worked.. hope this helps everyone.

also do this

https://tinkertry.com/speed-up-lotus-notes-8-5-3-or-ibm-notes-9-social-edition-under-windows-7-8-81-or-linux

TOPlist