Oxygen author Component slow performance with tables

[yury.eroshenkov]

Hello,
We integrated Oxygen Author Component to our web tool (Ditaworks) (if i'm not mistaken - it's a 15.0 version). Also we experienced with jars loading due to long applet initialization problem and excluded some ton necessary jars from jlnp - we are using the samr list of jars, which in the demo applet from your site are used.
Now we've faced with a performance problem in the editor in Author mode, especially with complex tables (when we have nested tables or tables with images and so on).
But, the demo applet from your site (http://oxygenxml.com/demo/AuthorDemoApp ... -dita.html) is working ok with the same content.
What can you suggest to fix the problem? Do we need to upgrade the component to the very last version or maybe excluding of some of the jars could affect?

[Radu]

Hi Yuri,

I am not familiar with your customization, do you use DITA or a DITA specialization? If you are using a DITA specialization, are the XML catalogs properly set up in the DITA framework bundled with the Author Component?
What exact operations are performed on the tables? Column deletions, row insertions, other?

If you enable the Java console and look into it while working with the large tables, are there any HTTP connections made? Because this would explain the slow down.

Regards,
Radu

[yury.eroshenkov]

Hi, Radu
No, we have no any DITA specializations and style customizations. The slowness is appear even while scroll the editor down-up. Typing, working with menu, scrolling - all activities are very slow when we have a complex tables.
About the http connections - i'l check it, but i don't think so.

Thanks, Yury.

[Radu]

Hi Yuri,

First you would need to check if there are HTTP connections made by the applet.
If there are not, you should try to update the Author Component Sample Project to the one which was released with Oxygen 15.2 (and which is used in our online demo as well) and see if it behaves better.
Or you could also try to profile the applet using JProfiler and see in what specific area of the code it hangs, maybe one of your customizations is the problem, do you have a custom StylesFilter set to it?

Regards,
Radu

[yury.eroshenkov]

Hi, Radu.
Thank you very much for your help. The problem was in our custom style filter.

Yury.

[Radu]

Hi Yuri,

The styles filter is called very often so as you probably found out you should cache as much data as possible there instead of computing different things every time the callback is received.

Regards,
Radu