Rick, I think the misunderstanding is that all clients fire the interval at the same time. This is not true, as there is no synchronisation between clients. What could be true (I haven't verified, but I can imagine), is that there's one "queue" that handles all interval activelinks, like the escalation queue on the server. So if you'd have multiple activelinks that fire on a 3 second interval, those activelinks would fire at the same time in the client (ar user or midtier). As the clients are not sychronized the load on the server is more randomized. For client side stuff the interval impact should be neglectable.
We're using the interval links in several places in our application ( www.expertdesk.com) and we haven't had any reports or proof of spikes in the server load when the interval links fire. Of course you should not be hitting the server every 3 seconds if it's not absolutely needed. And if you do, remember that it has impact on users that are using floating licenses, as each server interaction will renew the license token. Regarding the log files, I assume Doug was pointing at the client side log, as each "on interval" link would be logged to the workflow.log if you enable that. Hugo On 2/1/07, Rick Cook <[EMAIL PROTECTED]> wrote:
Doug, not that this is a big deal or anything, but if the earlier report that the 3 second interval AL was synced to happen all at once for multiple clients, that means that either there is C/S traffic, or that there is some variable set on the client as a result of the AL and form load. Plus, you mentioned that logs got larger when it was active. Were those client logs or server? I'm not picking at you, I just want to be as clear as I can be on some of the find points of how it all works. Rick -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Doug Blair Sent: Wednesday, January 31, 2007 4:08 PM To: [email protected] Subject: Re: Workflow All, Funny that this subject would come up like this, but just Monday I got a request to build the three second interval counter to show characters remaining. Works. I was concerned about performance too, so my test form has one active link that calculates the remaining space in 16 character fields (set fields X = 255 - LENGTH($field$) every three seconds (one set field action, 16 fields). The integer fields have no label, disabled change flag, and is displayed as text adjacent to each character field. If you watch closely Aruser's CPU was up by a (one) percent when this window is open, but you're only typing in one field at a time. No human-discernable pause, but the workflow log gets pretty large... There's no client-server traffic in this, networking's not an issue. Doug ____________________________________________________________________________ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
_______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
