Rapid update timing

["Card, Sandra" <scard@xxxxxxxxxx>]

I can't find the answer to this anywhere in the manual, csdirect, iug
listserv archives, etc.

There seems to be a definite difference in how rapid update transactions are
handled in the text INNOPAC and in Millennium.

When doing a rapid update in Database Maintenance in the text INNOPAC, the
transactions pause briefly after every 9th one before sending the next 9
through (I am normally rapid updating review files).

It looks like in Millennium Cataloging the rapid update pauses after every
25 transactions, except that the first 100 transactions are sent in so fast,
the pause is not visible until you get to 125 and so forth (at least on my
PC and Server).  Also, the pause for 25 transactions is apparently the same
as for 9 transactions (or too close for me to measure).

Why am I asking this?  Well, in the text INNOPAC I can do rapid updates at
any time without slowing down other transactions (especially circulation).
But now that I have used Mill Cat rapid update, I notice the transaction
file backing up slightly.  So OK, it adds maybe 1 or 2 seconds to the time
it takes Circulation to check out a book when we've got a couple hundred
transactions in the bibtemp file.  But they do notice delays  (so do I).



Sandra Card
Library
California State University, Los Angeles
scard@xxxxxxxxxx
323-343-4894



--- StripMime Report -- processed MIME parts ---
multipart/alternative
  text/plain (text body -- kept)
  text/html
---