thanks stephan , thierry and henrik I will use your code.
Alexander I would prefer to profile slow code, but sometimes profiling even
fast code gives more info about the internals of the system and what is
fast and what is slow and why.
On Sun, Nov 22, 2015 at 10:39 PM EuanM wrote:
> I was prof
I was profiling yesterday, and discovered these issues:
Issue:
=
Time and DateAndTime both show human-readable time information to
micro-second precision. Time also holds information to nano-second
precision.
Both objects are only providing information to the nearest millisecond.
The digits
Because profiling longer loops takes longer.
Why profile a 32768-cycle loop if a 2048-cycle loop would work?
On 22 November 2015 at 20:21, Alexandre Bergel wrote:
> Hi!
>
> Why do you need to profile fast code? You can always put your code in a loop.
>
> Alexandre
>
>
>> On Nov 22, 2015, at 4:22
Hi!
Why do you need to profile fast code? You can always put your code in a loop.
Alexandre
> On Nov 22, 2015, at 4:22 PM, Dimitris Chloupis wrote:
>
> yeah probably , your code returns nothing too. So what we suppose to use to
> profile fast code ?
>
> On Sun, Nov 22, 2015 at 9:12 PM Nic
rik
-Original Message-
From: Pharo-users [mailto:pharo-users-boun...@lists.pharo.org] On Behalf Of
Stephan Eggermont
Sent: Sunday, November 22, 2015 9:16 PM
To: pharo-users@lists.pharo.org
Subject: Re: [Pharo-users] About profiling code
On 22-11-15 20:42, Guillermo Polito wrote:
> Out of the top
On 22-11-15 20:42, Guillermo Polito wrote:
Out of the top of my head, doing it like that only profiles widget
creation/install if I'm not mistaken. But not render time.
Because the doit is executed inside the event processing of the morphic
render loop. But a cool ui profiling should also measur
Le 22/11/2015 20:42, Guillermo Polito a écrit :
Out of the top of my head, doing it like that only profiles widget
creation/install if I'm not mistaken. But not render time.
Because the doit is executed inside the event processing of the morphic
render loop. But a cool ui profiling should also m
Out of the top of my head, doing it like that only profiles widget
creation/install if I'm not mistaken. But not render time.
Because the doit is executed inside the event processing of the morphic
render loop. But a cool ui profiling should also measure the drawOn:
methods.
I don't know if there
yeah probably , your code returns nothing too. So what we suppose to use to
profile fast code ?
On Sun, Nov 22, 2015 at 9:12 PM Nicolai Hess wrote:
> 2015-11-22 20:01 GMT+01:00 Dimitris Chloupis :
>
>> Why
>>
>> [CheckboxMorph new] timeProfile
>>
>> returns nothing ?
>>
>
> too fast?
> [ 3+3 ] t
2015-11-22 20:01 GMT+01:00 Dimitris Chloupis :
> Why
>
> [CheckboxMorph new] timeProfile
>
> returns nothing ?
>
too fast?
[ 3+3 ] timeProfile
return nothing too.
try
[CheckboxMorph new openInWorld] timeProfile.
>
> I also tried it in the profile tool without the block and still displays
> not
Why
[CheckboxMorph new] timeProfile
returns nothing ?
I also tried it in the profile tool without the block and still displays
nothing . Is there any special requirement for profiling code ?
11 matches
Mail list logo