[p4] Why run Reviews as Daemons?

[Robert Cowham]

Actually I think it is largely historical that Perforce talks about daemons
since until relatively recently (2004.2 server) change-commit triggers did
not exist.

> The main advantage is performance. Doing anything other than 
> a quick query can me expensive and drastically slow down the 
> performance of your Perforce server.  A review daemon on the 
> other hand is a separate process. It can even be run on a 
> separate computer. Because it is completely separate from 
> Perforce is won't slow it down.

A change-commit is also a forked as a separate process, but it that runs on
the Perforce server machine, thus potentially impacting the Perforce server
itself (of course you can fire off a remote process but that starts getting
a bit messy).

My understanding is that no database locks are held while the commit trigger
runs so you are fairly safe there.

I haven't investigated potential race conditions with a second version of
the same trigger being fired off before the first one has completed. Anyone
investigated this?

Robert