> logicl...@yahoo.com wrote innews:1170771926.519649.217370@a34g2000cwb.googlegroups.com:
>
[quoted text clipped - 31 lines]
> Cheers
> GRB
On 7 fév, 11:43, logicl...@yahoo.com wrote:
> On 6 Feb., 20:59, "Greg R. Broderick" <gregb
>
[quoted text clipped - 40 lines]
> Thanks,
> Peter
If you are on windows, the resolution of the timer is about of 10 ms ,
unless you use the new System.nanoTime(), which resolution is much
finer, perhaps it's a problem of resolution of timer (for 0.1 - 0.2
sec, it's probably not the cause).
If the program use a database connection to retrieve the dataset,
perhaps the network or the database is busy during your test
The system is perhaps running another processes which use the CPU in
the same time
And if your program is multithreaded, other threads perhaps use the
CPU
So, there is multiple possible cause to explain your problem, we can't
tell much better without description of the system
(Sorry for my english, it's not my mnative language)