Benchmarking 7.0 performance

[Tim Selander]

Actually, I thought about an autosave. Tried an idler handler -- 
when 30 seconds of idle time accumulates, I figured that would 
indicate non-use, and I could execute a save without disrupting 
work flow. However, I couldn't make it work. Put it in the stack 
script but the idle handler never seemed to get called.  Probably 
the fact that I tried an idler handler shows how green I am as a 
programmer. How would you go about making one?

But back to my original inquiry, isn't 10 to 12 seconds to save a 
10MB file awfully long? Compared to everything else I do on a 
computer (words, spreadsheets, audio, video, photographs, ocr) it 
seems slow.

Tim Selander
Tokyo, Japan


On 10/28/14, 10:27 PM, Richmond wrote:
>
> On 10/28/2014 02:28 PM, Tim Selander wrote:
>> I don't know about benchmark on routines, but I have created a 
>> measly 10MB file -- customer database -- and saving changes to 
>> the file takes a full 10 seconds or more. That seems pretty 
>> slow to me. Duplicating the file in Finder takes a fraction of 
>> a second. Saving an edited 10MB .wav audio file takes a 
>> fraction of a second.
>>
>> Why is saving the stack so slow? This is going to be a real 
>> pain for my data entry lady who is used to HC saving 
>> everything automatically and invisibly....
>
> Possibly you need to be kind to your data entry lady and build 
> an autosave routine into your stack.
>
> Richmond.
>
>>
>> OSX, MacBook Pro i7, 1TB internal HD.
>>
>> Tim Selander
>> Tokyo, Japan
>>
>>
>> On 10/27/14, 10:44 PM, Geoff Canyon wrote:
>>> I'm wondering if anyone has benchmarked 7.0 performance? I 
>>> did two quick
>>> tests and found:
>>>
>>> on mouseUp
>>>     put the long seconds into T
>>>     repeat with i = 1 to 20000000
>>>        put "A" && "aa" into X
>>>     end repeat
>>>     put the long seconds - T
>>> end mouseUp
>>>
>>> Took almost 5x as long to run as on 6.7, which I expected 
>>> since it's
>>> presumably doing UTF things under the hood.
>>>
>>> But I also found:
>>>
>>> on mouseUp
>>>     put the long seconds into T
>>>     repeat with i = 1 to 20000000
>>>
>>>     end repeat
>>>     put the long seconds - T
>>> end mouseUp
>>>
>>> Took about 1.5x as long to run on 7.0 as on 6.7. Obviously 
>>> our own code is
>>> still a much larger factor -- "repeat for each" in 7.0 is 
>>> still going to
>>> handily beat "repeat with" in 6.7 for processing large chunks 
>>> of text, etc.
>>>
>>> gc
>>> _______________________________________________
>>> use-livecode mailing list
>>> use-livecode at lists.runrev.com
>>> Please visit this url to subscribe, unsubscribe and manage 
>>> your subscription preferences:
>>> http://lists.runrev.com/mailman/listinfo/use-livecode
>>>
>>
>>
>> _______________________________________________
>> use-livecode mailing list
>> use-livecode at lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage 
>> your subscription preferences:
>> http://lists.runrev.com/mailman/listinfo/use-livecode
>
>
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your 
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>