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

Task limit in TS 5.5.2 on W2K?

Bowker

ts 5.5.2
win 2K

A while back I posted the question of "is there a limit to the number of tasks a job can have?" I don't remember the response for TS 5.5.2. Under 5.0 there was a limit, but is there a limit in 5.5.2?

If so, what is a safe limit?

Find more posts tagged with

Comments

Adam Stoller

I'm not sure there's a limit to the number of tasks a job can have, but there are some performance degradation issues with having a large amount of tasks defined in the system (I don't remember the exact numbers, and unfortunately my memory with regard to this point has a wide berth - anywhere from 2,000 to 50,000) Assuming the lower limit (which is thus definitely lower than the higher limit) you should try to make sure that at any given point in time you have fewer than 2000 tasks defined in the system. To get an idea of how many tasks you have in the system - create a file that contains this (taskquery.xml):

<taskquery><or><active/><not><active/></not></or></taskquery>

And then (on Unix) run this command:

% iwquerytasks < taskquery.xml | wc -l

(if you're on Windows and don't have unix-like tools handy, not sure what the best way is to arrive at a count - I can think of several ways, but I've never had to do that since I always hace unix-like tools on my laptop)

--fish
(Interwoven Senior Technical Consultant)

nipper

Interesting little script fish, since I just ran it & it 1500, is there any way to get a closer range than 2K to 50K ?

Hardware dependant ? Memory ?

Andy

Bowker

I'm actually referring to iterations within a job. I want a specific workflow to repeat every 5 minutes forever.

How bad is that?

P.S. I only have 325 active|~active tasks on my system now.

Adam Stoller

I'm kind of hoping someone with more factual information will follow-up with the more realistic numbers and, if possible, the environment in which they were obtained (I'm don't have access to much other than DevNet right now - and unless I or someone else already posted more precise numbers [I didn't look, don't really have the time right now] you'll just have to wait for someone else to supply the numbers). If you aren't seeing any noticable performance degredation at 2000 tasks, then maybe it was somewhere between 20,000 and 50,000 (which would at least be in the same relative ballpark). I imagine that memory and the ability to process information in memory quickly would be the prime candidates for performance boosting in this area.

(If only we had TeamSite running on MacOS-X - I'd love to see what it would do on a Dual-CPU G5 with 8Gb RAM and 64-bit processing....)

--fish
(Interwoven Senior Technical Consultant)

Adam Stoller

Iterations of a job - again burried in the recesses of my mind, I think I recall some limitation of 1000 iterations - and that might be more due to limitations on storing / tracking all the event history than on general performance [though one could consider them linked I suppose].

Usually if someone is talking about having a job constantly re-running - it's a sign of not using the tool in a well designed manner.

My guess (since you haven't provided more detailed information) is that you are processing some sort of "hot-box" where files get placed and you want to swoop in every 5 minutes to pull them out and process them somehow. If that's the case - you'd be better off creating a job description file and for the workflow and running a 'cron' or 'at' job to check the directory, and if there are new files present to be processed, kick off a new instance of the job at that point in time.

--fish
(Interwoven Senior Technical Consultant)

shanon

to ghoti's point... if you say that you want something to repeat every 5 minutes forever, that something should run as a scheduled task / cron / at script.

keep it simple: write the workflow to do your job once, then cron it up for every five minutes.

if you man cron and crontab, you can get all the info you need... just make sure that you cron it as a user that has permission to do all of the tasks in your workflow -- this has caused some headache in the past...

hope this helps.

Shanon Levenherz
Mercer eBusiness Team
shanon.levenherz@mercer.com
http://www.mercerhr.com

james1

There is a hard limit of 1000 on either (a) the number of task activations in a single job, or (b) the number of task completions in a single job, or (c) both.

If you had a job that ran in a loop forever, you would hit this limit sooner or later.

-- James

--
James H Koh
Interwoven Engineering

Bowker

Perfect - that's what I was looking for - not the answer I wanted but thanks.

P.S. Not all of us have the ability to run AT commands on the TS server Smiley Sad