nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Why is the templating tool so slow?

gartmorefunds

We are using the web-based UI for Teamsite version 5.5.2. When we create DCRs for pages that would be the equivalent of 2 or more printed pages, the process of adding or deleting replicants (individual paragraphs, bullets, headings, table rows or columns, etc...) takes up to two minutes each. The server is a single processor Netra box running Solaris. The client machine is a P4 with 384 MB of RAM, running at about 2 GHz.

Why does this process take so long? It is futile to use TS to generate pages this way.

Find more posts tagged with

Comments

vlahogiannis

we have had some lousy performance on the template side, but only when perfoming actions on the server such as saving, or generating.

this sounds like a browser issue cause your desktop machine sounds ok. Perhaps you have way too much content in your dct. also, you should clean out your browser page cache and kill any unnecessary applications running on yoru desktop. this should buy you some performance.

goodluck. -gv

Migrateduser

What browser are you using? Are there VisualFormat elements in the templates? Can you construct a simple test case, with say on of the example templates, that would give you a baseline.

Just some suggestions. Regards,

lissa

I0000000310.txt

Migrateduser

our templating performance is poor also, with slowness and constant IE crashes

we have brand new machines w/ winxp and ie 6 sp1

IW seems to always point the cause to the VFE...and their solution is to put it into a seperate callout (which is not acceptable for our clients)

however, our crashes often occur when a user adds a replicant or clicks save and close. the performance degrades significantly w/ each replicant added to the DCT.

---------------------
Eric B.
Federated Investors
AOL IM: arthas76

Migrateduser

I am not saying the problem is VisualFormat, merely trying to collect data. THe way VF is integrated with TeamSIte, we make an instance of the control for each VF call. This has been changed in TeamSite 6.0, alleviating this performance bottleneck. Note that this is not a VF problem, but it is a problem you run into when you use a lot of instances with VF.

It sounds like some folks are seeing issues with replicant performance. If this is the case, it would be helpful to know specifcally what TS and Templating SP level, etc.

I did a quick look on the fixed bug list for SP3, and found this one: link to bug list - https://support.interwoven.com/library/manuals/templating/templating.asp

34219 Calling refreshForm() from a CGI callout can result in a long delay if the form has many items or replicant instances.

I cannot tell from the posts what TeamSIte version you are on. This data would be very helpful.

lissa

gartmorefunds

Thanks for the comments. How does the VFE affect the time to create or delete a replicant? All we have is the VFE button to the right of each text box, but it is rare when we use it for anything. Is it that each VFE button generates a separate instance? If so, why does that make it take so long to add or delete a replicant?

The version of TS is 5.5.2 with SP1. The browser is IE.

Migrateduser

Based on the SP2 and SP3 fixed bug lists, I recommend moving up to a later SP. I also believe tech support is pretty well versed in replicant questions, you may want to file a support case. I'll see if I can get someone to respond to your specific question on VF and replicants.

Regards,

lissa