Hi Doug,
My bad... the getTickCount() in the snippet is basically
a wrapper over ftime call, and the same is used on the
linux platform also for timing.
time_t getTickCount()
{
timeb tm = {0};
ftime(&tm);
return ( (tm.time*1000) + ((time_t)tm.millitm) );
}
Thanks & Regards
Nitin K
On 3/13/07, Doug Nebeker <[EMAIL PROTECTED]> wrote:
Be aware that the Windows GetTickCount call has a resolution of 10 to 15
ms on most machines, so that could throw throw your timings off if
you're timing each individual test case as it appears below. To get
better timer resolution, use QueryPerformanceCounter.
Now, would that make SQLite3 looks slower than v2? I wouldn't think
so--you'd think it would skew the results equally for both tests.
Doug
This email was sent to you by Reuters, the global news and information
company.
To find out more about Reuters visit www.about.reuters.com
Any views expressed in this message are those of the individual sender,
except where the sender specifically states them to be the views of
Reuters Limited.
Reuters Limited is part of the Reuters Group of companies, of which
Reuters Group PLC is the ultimate parent company.
Reuters Group PLC - Registered office address: The Reuters Building, South
Colonnade, Canary Wharf, London E14 5EP, United Kingdom
Registered No: 3296375
Registered in England and Wales
