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

Maximum Size of DCR

System

What's the maximum size (in KBs) of a DCR Interwoven TeamSite can hanlde?

Find more posts tagged with

Comments

raviswamy

Did you get any answer for this. I would like to know. Guess, I am having a similar issue. Trying to open a DCR which is 41K. Do let me know

stefanmaier

Hello,
we have DCRs up to a maximum of 540KB.
TeamSite can handle our DCRs, but we have some performance problems on our clients (IE6.0SP1 and Firefox 1.0).
If you try to save an large DCR, there is a lot of clientside JavaScript, which runs some minutes...

Regards

Stefan

Migrateduser

Just a quick note about FormsPublisher performance. The TS 6.1 SP2 release notes says there was a bug fix for performance with javascript in DCRs.

See bug 52594 on this page on DevNet:
http://devnet.interwoven.com/site.fcgi/browse/ts6/DevNet-TS6.html#TS61SP2

hth,

lissa

stefanmaier

Hello Lissa,
thanks for that hint, actually we are evaluation TS6.5, I hope, javascript-performance is better there...

Regards
Stefan

Migrateduser

One important thing to remember here is this is an web application. The bigger the DCR file size, the longer it is going to take to bring it over the network, which can be really painful depends upon their network bandwidth.

Secondly, the more replicants you have, the slower it is going to be since it is use Javascript to try to build the form and set the values for them.

It's really hard to give a firm line on the max limit as you can see.

Migrateduser

Serving the file over the network is rarely the problem with DCRs. Even a HUGE DCR is typically going to be under 250KB. The rendered HTML will likewise be pretty small. I imagine it would be pretty hard to accurately track the time used to render the DCR, but you could do a rough back of the napkin estimate:

Render Time = TotalTime - (RenderedHTMLSize/Avg. Network Thruput)

Migrateduser

Guess you're sort of right on the size, though it does play a big role if you are on a dialup or T1 line. Secondly, the more items you have on the DCR, the longer it takes to load the form. The way templating works is using frames. The bottom frame is used to first load all the elements of the DCR in Javascript, then it is executed to load the middle frame to build up the form. This has a lot of dependency on the client's machine, the more elements in the DCR, the longer it takes to load the form, which means size of DCR and number of elements are very important factors in the DCR rendering time.

Migrateduser

Frames are gone in 6.x. They claim that the render time is much improved. I don't have any of my old huge DCRs from my previous project around or I would test that assertion. Gut feel, it seems slower on small DCRs than it used to be.

Migrateduser

It just occured to me that you might still get frames if you have the navigation pane turned on, which I do not. I think off is the default now.