[etoys-notify] [JIRA] Updated: (SQ-708) Tick Rate not accurate

Bert Freudenberg (JIRA) tracker at squeakland.org
Wed Jun 2 05:43:16 EDT 2010


     [ http://tracker.squeakland.org/browse/SQ-708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bert Freudenberg updated SQ-708:
--------------------------------

    Fix Version/s: someday
         Priority: Eventual  (was: Normal)

Etoys is not a real-time system. The ticking rate is is the desired number of script executions per second. The actual number can be lower depending on how much else is going on. Faster machines will run closer to the desired number of ticks, slower machines less so.

I'll keep this ticket open in case someone else thinks this is a bug, but fundamentally this cannot be resolved within the current implementation.

> Tick Rate not accurate
> ----------------------
>
>                 Key: SQ-708
>                 URL: http://tracker.squeakland.org/browse/SQ-708
>             Project: squeakland
>          Issue Type: Bug
>          Components: etoys
>            Reporter: Stephen Thomas
>            Priority: Eventual
>             Fix For: someday
>
>         Attachments: TickRateTest.001.pr
>
>
> Saw problems with Tick Rate while running random number tests. Created a simple project (see attached)
> to check tick rate by having a script to increment a counter and another to start it and then stop it after N seconds.  Below are some of the results
> Tick Rate - Counter Value After 10 seconds
> 1 - 10
> 2 - 20
> 5 - 50
> 8 - 72
> 10 - 98
> 25 - 230
> 50 - 384-405
> 100 - 500
> Also ran at tick rate of 100/sec for 100 seconds and got counter values of 4975 to 5000
> May be related to SQ-124

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tracker.squeakland.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the etoys-notify mailing list