Windows command prompts allow for a time stamp to be placed as the command starts and one as it ends. I don't know if time counts the time elapsed or the amount of CPU-time that a command takes up, but the windows one timestamps, runs command, and timestamps.
Michael Potts (904) 638-2914 On Mon, Nov 8, 2010 at 4:33 PM, William L. Thomson Jr. < [email protected]> wrote: > On Mon, 2010-11-08 at 16:16 -0500, Michael Potts wrote: > > Was querying Google.com using Window's nslookup tool (nslookup > > google.com208.67.222.222). > > Is that what was reporting the times? You can see the times reported by > dig and time on Linux differed a bit. > > > Uncached attempts using OpenDNS's 208.67.222.222 on Mac (I hate to use > this > > network as the benchmark, its quite loaded down) and the poor Macbook is > > doing a USB file transfer. > > Network is kinda moot, I was more curious on if there was any delay > coming from a different networking stack. Since Linux tends to be faster > than Windows at most network related operations. > > Crazy to say the network is moot, since delays can come from that and be > passed on. But in reality so many variables, starting with usage of the > nic on the local machine :) > > Almost need a dead inactive machine and network to do pure tests without > any other factors. Then there is still the real world out there, and I > doubt any query would be exactly the same time wise. > > -- > William L. Thomson Jr. > Obsidian-Studios, Inc. > http://www.obsidian-studios.com > > > --------------------------------------------------------------------- > Archive http://marc.info/?l=jaxlug-list&r=1&w=2 > RSS Feed http://www.mail-archive.com/[email protected]/maillist.xml > Unsubscribe [email protected] > >
