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; } } }

Rules of thumb for Replicants

awgolk

Is there any good rules of thumb for a good max number of replicants allowed per template? Is the threshold for where the number of replicants begin to bog down the users machine? Does increasing the RAM on the system help combat this?

Find more posts tagged with

Comments

nipper

Most replicants, a high number. (I have seen hundreds)

However if you are using the visual formatter then the number is much lower. Since that is
an active X app, I would avoid more than 20.

What widgets in the replicant are you considering ?

awgolk

we have a request to allow up to a couple of hundred of replicants with around 4-5 with one being a Visual Format Field. We currently are working with 6.1 and moving to 6.5, so that should improve the situation but I have not seen about how much this improves it.

nipper

Benchmark it. However I would be very surprised if this works consistantly. In 5.5 each instance
of VFE was another app running, at a couple MB per, 200 would drop the PC to its knees. I have not
tried it in 6.X

even worse is if it works in a lab & fails over the network, on older computers, etc. Support nightmare.

cliffhanger

We had a template with only few items(most probably 3) in a replicant and only one of them being VisualFormat item, whenever the replicant number exceeded 50, we would see it chewing up system CPU, and it would become unresponsive when it reaches 100.

Adam Stoller

You need to clearly distinguish between experiences prior to 6.x and experiences post 6.x.

Prior to 6.x, the accepted strategy for dealing with Visual Format fields was to make the VFE an external / callout editor rather than an inline editor - because it used ActiveX technology and would create as many ActiveX processes/objects as there were internal VFE fields.

With 6.x, Interwoven / Ektron (one, the other, or both) fixed things so that regardless of having the VFE fields inlined, only one VFE field would be "active" at any one time. You could still use the external callout interface, but you can now leave the editor interface inline without paying as high a penalty as in prior versions.

All that being said - you still need to figure out if you want to use VFE (it's rather limited in terms of platform and/or browser support, rather clunky and confusing customizations, etc.), plain text areas, or callouts for running other WYSIWYG-type editors (there have been several threads on this)

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

cliffhanger

The experience mentioned in my previous reply was on TS 6.1.

Adam Stoller

Interesting. Did you report it to Support with a DCT (or two) to replicate the situation?
My customer's gotten rid of the one VFE field we had during the 6.5 upgrade - so this is not really an issue for us (thankfully).

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

cliffhanger

No we haven't.
We are also exploring other alternatives of VFE since it seems to be evermore troublesome in 6.5. It has all kinds of issues(let me know if you are interested in the list

), many of them are already posted in devent by other users.

awgolk

I am intrested in a list

cliffhanger

Two of them are mentioned in this thread:
http://devnet.interwoven.com/forums/cgi-bin/showflat.pl?Cat=&Board=PRODUCTS_TEMPLATING&Number=59216&page=&view=&sb=&o=&vc=1

-if you click too quickly from one VFE field to another it gives "null item found error"