Phil Ehrens wrote:
>Don't create a seperate lam user for each user, but DO create
>more than one. If one account suffices when no failures occur,
>and if failures costs you 50% of your duty cycle, have two users,
>and so forth, using them in round-robin fashion. That's what we
>do, and we achieve job rates of > 2000 jobs per hour over weeks
>of running.
>
>
>
>
I tried once a workaround like this, using the session prefix feature,
but sometimes the lamboot command hung, and it became hard to debug and
maintain.
If I has to spend so more time, I'd prefer improving LAM than my private
software, kind of deserved contribution :-)
|
