on-rev example: 'globals.cgi' conversion

[Mark Smith]

I guess we'd expect it to be faster from within the US (data centre  
is in Texas, I believe), but the difference in cgi/irev seems similar.

Ian -  maybe your ISP has been hitting the cider :)

best,

Mark

On 18 Apr 2009, at 21:10, Jim Ault wrote:

> Changed the last line of your script to
>
>    get "irev:" & tTimA && tResA & cr & "cgi:" & tTimB && tResB
>    put msg & cr & cr & it into msg
> --to concatenate results
>
> After waiting 30 seconds,
> 4 clicks 1 second apart = 4 results listed below -----
>
> irev:115 md5-hmac = 7e5872da5d34a822584a698fe7db6c10
> cgi:83 md5-hmac = 7e5872da5d34a822584a698fe7db6c10
>
>
> irev:55 md5-hmac = 7e5872da5d34a822584a698fe7db6c10
> cgi:89 md5-hmac = 7e5872da5d34a822584a698fe7db6c10
>
>
> irev:60 md5-hmac = 7e5872da5d34a822584a698fe7db6c10
> cgi:88 md5-hmac = 7e5872da5d34a822584a698fe7db6c10
>
>
> irev:55 md5-hmac = 7e5872da5d34a822584a698fe7db6c10
> cgi:73 md5-hmac = 7e5872da5d34a822584a698fe7db6c10
>
>
> Jim Ault
> Las Vegas
>
> On Apr 18, 2009, at 12:44 PM, Mark Smith wrote:
>
>>
>> On 18 Apr 2009, at 20:24, Richard Gaskin wrote:
>>>>
>>>
>>> The CGI is indeed fast, but if the timing is being measured  
>>> inside the script it's not accounting for the biggest difference  
>>> between the CGI and on-Rev:  on-Rev has no load time to bring the  
>>> engine into memory and initialize it since it's already loaded  
>>> and running, while the CGI engine has to be loaded fresh each  
>>> time it's called.
>>>
>>> Even with that extra overhead the Rev CGI measures well against  
>>> equivalent CGIs, but I'd be surprised if it could beat on-Rev.
>>>
>>> --
>>>
>> if you put this in a button you can see another test:
>>
>> on mouseUp
>>   put "http://marksmith.on-rev.com/mashash/hashmac.irev? 
>> data=somedata&key=somekey&action=md5hmac" into tIrevUrl
>>   put "http://marksmith.on-rev.com/cgi-bin/hashmac.cgi? 
>> data=somedata&key=somekey&action=md5hmac" into tCgiUrl
>>
>>   put the millisecs into ts
>>   put url tIrevUrl into tResA
>>   put the millisecs - ts into tTimA
>>
>>   put the millisecs into ts
>>   put url tCgiUrl into tResB
>>   put the millisecs - ts into tTimB
>>
>>    put "irev:" & tTimA && tResA & cr & "cgi:" & tTimB && tResB
>> end mouseUp
>>
>> I'm seeing the cgi taking 190-200 ms and the irev taking 170-180 ms.
>>
>> The irev is 'including' a textified version of my hash/hmac  
>> library, and the cgi is loading a stack which inserts the library  
>> (and a few others) into back, so perhaps the test is slightly  
>> skewed in irev's favour.
>>
>> I'll leave it up for a few hours if anyone wants to try it out  
>> (I'd also be interested in other people's timing from different  
>> places - I'm in London).
>>
>> Best,
>>
>> Mark
>> _______________________________________________
>> use-revolution mailing list
>> use-revolution at lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your  
>> subscription preferences:
>> http://lists.runrev.com/mailman/listinfo/use-revolution
>
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your  
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-revolution