Basically, if you have one large schedule for lots of clients and you're in
polling mode, you don't want to slam your server with 500 simultaneous
sessions. Randomization lets the sessions start scattered randomly across
the first n% of the schedule.
Of course, if you have few clients per server or your operational philosophy
is to create lots of short schedules with few nodes, the randomization
doesn't have much effect.
-----Original Message-----
From: Johnn D. Tan [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 24, 2001 1:03 PM
To: [EMAIL PROTECTED]
Subject: Re: The TSM FAQ needs your help
>As you are probably aware, the TSM mailing list does not have a frequently
>asked questions (FAQ) list.
What does the "Schedule Randomization Percentage" mean, exactly? Your
FAQ-O-Matic says to set this to 0. We have it at 50. I've inherited
this system, so was not the one who set this. But what are the
trade-offs? If it was always better to have it at 0, why would they
give you an option?
