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.
Karl Forner wrote:
> Hello,
>
> I recently sent a mail about a bug that annoys me, because I'm using lam
> in a very particular way.
>
> I deal with a lots of fast mpi jobs (sometimes just a few seconds) from
> many differents users.
> These jobs are can be very fast so that it is no-sense starting a new
> lam session at each time (on my cluster a lamboot usually takes around 5
> seconds).
>
> Moreover I do not want to create as many accounts as I have different
> users, so I only use one lam-session.
> So if something goes wrong (crash, signal (CTRL+C)), it is difficult to
> cleanup the session because other jobs could be running at the same time.
>
> What could help me, is for example to be able to do a kind of lamclean,
> but just for a given mpi job : for example
> % lamclean lam_id
>
--
Phil Ehrens <pehrens_at_[hidden]>| Fun stuff:
The LIGO Laboratory, MS 18-34 | http://www.ralphmag.org
California Institute of Technology | http://www.yellow5.com
1200 East California Blvd. | http://www.total.net/~fishnet/
Pasadena, CA 91125 USA | http://slashdot.org
Phone:(626)395-8518 Fax:(626)793-9744 | http://kame56.homepage.com
|
