[self-interest] UI Performance Question

[Michael Latta]

The X frame rate was the same as before: 9-12 fps on a screen with only 
the frame rate meter and a shell.

Any other ideas?

Michael



On Jun 16, 2004, at 2:22 AM, ungar at mac.com wrote:

> Michael,
>
> Are you using X or Carbon? It may have to do with the way the VM gets 
> Carbon events.
> Try starting an X server, doing an xhost +, then saying
> desktop openNewWorldOnDisplay: ':0.0'
>
> - David
>
>
>
> On Jun 15, 2004, at 3:03 PM, Michael Latta wrote:
>
>> Thanks for the pointer, but that does not seem to be the issue.
>>
>> If I use 120 it starts to slow down, but anything less gets the same
>> 8-10 fps.  The times are very consistent between two very different
>> machines: 1Ghz G4 and 2.0 Ghz G5.
>>
>> Self is only taking about 5% of the CPU to get 8-10 fps.  If I could
>> get it to use more it would be very acceptable frame rates!
>>
>> Is it the semaphores?  It looks like Self is not using OS threads so 
>> it
>> should not need OS semaphores.
>>
>> Any other ideas or ways to track down what is the issue would be
>> welcome.
>>
>> Michael
>>
>>
>>
>> On Jun 15, 2004, at 2:08 PM, Jecel Assumpcao Jr wrote:
>>
>>> On Tuesday 15 June 2004 13:18, Michael Latta wrote:
>>>> I am new to Self but have been poking around.  The frame rate in 
>>>> Self
>>>> seems a bit low for me, and was poking around to find what is the
>>>> issue.  On my G4 1Ghz I get 8-10 fps, but on my dual 2.0 G5 I also
>>>> get 8-10 fps.  This leads me to believe there is some attempt to 
>>>> make
>>>> the fps a fixed number rather than being driven as fast as possible.
>>>> But I have not been able to locate any timer based throttling of the
>>>> step processing for activities.  Any pointers would be welcome.
>>>
>>> Method 'runLoop' in traits worldMorph in includes this line
>>>
>>>   delayIfNoInputFor: (desiredFrameTime - computeTime) max: 0.
>>>
>>> and 'desiredFrameTime' is defined in traits worldMorph itself as 35.
>>> Supposing that is milliseconds, then we should be throttling to some 
>>> 28
>>> frames per second or so. Changing that to 15 didn't seems to have any
>>> effect (on a 600MHz PC) while making it 8 did. I also tried 60 which
>>> didn't seem to make it slower, but then 300 dropped to 3 frames per
>>> second.
>>>
>>> -- Jecel
>>>
>>>
>>>
>>> Yahoo! Groups Links
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>>
>>
>> Yahoo! Groups Links
>>
>>
>>
>>
>>
>