Re: Checking the Milliseconds

2021-04-08 Thread Keith Martin via use-livecode
I ran the original code on my MacBook Pro (16in 2019, 2.3GHx 8 core i9). Three quarters of the results were over 4000, almost 150 of those were 4400 or above. The highest value was 4493. Average: 3873 (rounded) Median: 4081 Standard Deviation: 611 (rounded) k __

Re: Checking the Milliseconds

2021-04-08 Thread Craig Newman via use-livecode
Hi. I rand this a few times on an iMac 3.2Ghz Intel I5 I got very consistent counts, averaging 2605, and most count deviating very little from that value Craig > On Apr 8, 2021, at 1:24 AM, Mark Wieder via use-livecode > wrote: > > On 4/7/21 9:38 PM, Tom Glod via use-livecode wrote: >> I he

Re: Checking the Milliseconds

2021-04-07 Thread Mark Wieder via use-livecode
On 4/7/21 9:38 PM, Tom Glod via use-livecode wrote: I hear you Sean ..it is pretty interesting These are like gritty details about the engine, and I love learning them. I did not expect less than a microsecond / operation, thats for sure. There are a few other operations I would like to test

Re: Checking the Milliseconds

2021-04-07 Thread Tom Glod via use-livecode
I hear you Sean ..it is pretty interesting These are like gritty details about the engine, and I love learning them. I did not expect less than a microsecond / operation, thats for sure. There are a few other operations I would like to test in this way. thanks for reminding me about the detail

Re: Checking the Milliseconds

2021-04-07 Thread Sean Cole (Pi) via use-livecode
Hi Tom It is really interesting to see the results from this though. Tried it on my various machines and got pretty much the same results as everyone else consistently. It's amazing to see that in the region of 3000 loops occur in the period of 1ms. which means we are perhaps getting 1 (lowish lev

Re: Checking the Milliseconds

2021-04-07 Thread Tom Glod via use-livecode
Excellent ... Yes the 1st one was usually the one that was the lowest for me, for the reason you described. But you also cleared up the mysterious big jumps,I too now get a consistent result. Thanks for chimming in On Wed, Apr 7, 2021 at 3:59 PM Niggemann, Bernd via use-livecode < use-livecode@li

Re: Checking the Milliseconds

2021-04-07 Thread Niggemann, Bernd via use-livecode
I tried this and got pretty constant results except for maybe the first ten iterations. I figured if you just jump in with the milliseconds you would not be at the "beginning" of the milliseconds and added a repeat loop to mitigate that effect. Furthermore I appended the result to a variable.

Re: Checking the Milliseconds

2021-04-07 Thread Tom Glod via use-livecode
I think I realized the problem will test to confirm. I think the Max is actually what the avg should be. I think the writing to the variable is what increases the time between those queries. On Wed, Apr 7, 2021 at 12:58 PM Ralph DiMola via use-livecode < use-livecode@lists.runrev.com> wrote:

Re: Checking the Milliseconds

2021-04-07 Thread Tom Glod via use-livecode
I closed everything down to make sure the core was being used as little as possible. It didn't make a difference in the counts or the variance I reported earlier. I guess its not important, but it sure is curious. I think it means the engine is busy with something most of the time, and once in a wh

RE: Checking the Milliseconds

2021-04-07 Thread Ralph DiMola via use-livecode
I added an average. i7-6700 3.4GHz 8 cores in the VM Run 1: Max==>4586 Min==>460 Average==>3096.058 Run 2: Max==>7573 Min==>460 Average==>3835.764743 Run 3: Max==>7573 Min==>728 Average==>2947.388 Interesting Ralph DiMola IT Director Evergreen Information Services rdim...@evergreeninfo.net

RE: Checking the Milliseconds

2021-04-07 Thread Ralph DiMola via use-livecode
I scanned the results after it was done and got this: Max==>3959 Min==>1015 Ralph DiMola IT Director Evergreen Information Services rdim...@evergreeninfo.net -Original Message- From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf Of Tom Glod via use-livecode Sent

Re: Checking the Milliseconds

2021-04-07 Thread Tom Glod via use-livecode
Hmmm I averaged about 3500. but every so often 7000+. On Wed, Apr 7, 2021 at 12:17 PM Ralph DiMola via use-livecode < use-livecode@lists.runrev.com> wrote: > Here's the first few from LC 9.6.1 Win 10 Pro VM SSD > > 1473 > 3326 > 3397 > 3155 > 2442 > 3234 > 2292 > 3349 > 3380 > 327

RE: Checking the Milliseconds

2021-04-07 Thread Ralph DiMola via use-livecode
Here's the first few from LC 9.6.1 Win 10 Pro VM SSD 1473 3326 3397 3155 2442 3234 2292 3349 3380 3275 3259 3498 3300 3634 3462 3228 3896 3762 3197 3186 2188 1461 2716 3358 2940 2886 2614 2264 3038 3322 3305 3372 3395 3418 2579 Ralph DiMola IT Director Evergreen Information Services rdim...@ever

Re: Checking the Milliseconds

2021-04-07 Thread Tore Nilsen via use-livecode
It averages around 3850 and 3900 every time I try. However, when I try to run the test 1 times the average goes down to just above 3600. BigSur on Xeon W 3GHz. Best regards Tore Nilsen > 7. apr. 2021 kl. 18:03 skrev Tom Glod via use-livecode > : > > Hey peeps, > > I wanted to measure how