I realize that. The way NAV works is that the scanner process itself does the scanning on behalf of the invoking process and thus gets the CPU, or that's my limited understanding. But like I said, the problem disappeared after another update from Symnatec, so they must have corrected whatever the problem was. So this turns into just an FYI in case you see a similar problem, in which case you may want to do a LiveUpdate to correct the issue (if it's not happening automatically).
Peter Reilly <[EMAIL PROTECTED]> wrote on 12/11/2003 01:15:36 PM: > [EMAIL PROTECTED] wrote: > > >For those that may have wondered, below is the result some timing tests I > >was getting using Cygwin's time tool. > > > >With Auto-Protect enabled: > >D:\dev\java>c:\cygwin\bin\time d:/ant/bin/ant.bat -version > >Apache Ant version 1.5.4 compiled on August 12 2003 > >0.01user 0.73system 2:33.87elapsed 0%CPU (0avgtext+0avgdata > >6720maxresident)k > >0inputs+0outputs (421major+0minor)pagefaults 0swaps > > > > > > > The 0%CPU means that not much has been given to your process, > 0.01 user + 0.73 syse ~ 1Second as against 2 1/2 elapsed time.
