FWIW: I think this is a dev question, not a users question. On Mon, Sep 20, 2004 at 08:30:34PM -0700, Robert Menschel wrote: > I've managed to get my nightly mass-check run operational.
:) yea! > I still need to work on my weekly --net enabled check -- haven't had one > of those complete yet, but the daily (local) mass-check runs to > completion successfully. FWIW: I've found I need to disable DCC. It works fine in my normal workload, but dies under heavy mass-check load. > Just checking ... the mass-check process kicks off at 02:10 am PDT. It > runs for about 7 hours, finishing up this morning at 09:03 am PDT (09:13 > if you count the rsync of results back to the server). So 2:10 PDT is 9:10 GMT (I think that's right), finishing up at ~16:00PDT. > Is this a usual/acceptable elapsed execution time? If everyone else's > mass-check runs in only 2-3 hours, then I'd like to know so I can find > out why mine takes so long. If everyone else's takes the same ballpark, > then I'm happy with what it does. I think that's fine for a general start time -- I start mine at ~5:11 EDT, aka 9:11 GMT. My run takes ~20 minutes for set0. 24k messages. So 7 hours is a bit, but depends on what type of system you're using, how many messages you're processing, etc. -- Randomly Generated Tagline: Can I yell "movie" in a crowded firehouse?
pgpbtsaxDukYt.pgp
Description: PGP signature
