2010/7/1 Simon Marlow :
> So one option is to make a new CCS root for each thread, and that way each
> thread would end up creating its own tree of CCSs. That would seem to work
> nicely - you get per-thread stacks almost for free. Unfortunately it's not
> really per-thread profiling, because if o
On 23/06/2010 18:44, Henrique Ferreiro wrote:
2010/6/15 Simon Marlow:
On 15/06/2010 16:28, Henrique Ferreiro wrote:
I got the most important pieces working (I think). The question now
is, are you interested in this?
It all depends on whether other people would find it useful or not. At the
2010/6/15 Simon Marlow :
> On 15/06/2010 16:28, Henrique Ferreiro wrote:
>
>> I got the most important pieces working (I think). The question now
>> is, are you interested in this?
>
> It all depends on whether other people would find it useful or not. At the
> moment I'm not convinced that profil
On 15/06/2010 16:28, Henrique Ferreiro wrote:
I got the most important pieces working (I think). The question now
is, are you interested in this?
It all depends on whether other people would find it useful or not. At
the moment I'm not convinced that profiling each Capability separately
wil
> I'm not sure it's useful to profile each Capability separately. Threads
> migrate between Capabilities under the control of the runtime system, so you
> won't get the same results from run to run.
But even in that case, I get to know what is happening in each
capability, so I can get an idea of
On 14/06/2010 08:39, Henrique Ferreiro wrote:
Sorry for the late replay, I thought I made it work but I am still
fighting with it.
Do you really need to do this? Why not share the stacks and use a mutex to
protect the operations?
My idea is to allow for profiling of each capability, so I nee
Sorry for the late replay, I thought I made it work but I am still
fighting with it.
> Do you really need to do this? Why not share the stacks and use a mutex to
> protect the operations?
My idea is to allow for profiling of each capability, so I need to
keep the stacks independent of each other
On 10/06/10 18:06, Henrique Ferreiro wrote:
Hi!
I manage to make it work with one capability. That is, now the CCCS is
stored per capability but I can't enable parallel profiling because
the stacks are still shared.
Now I wanted to have one instance of each stack and cost centre per
capability,
Hi!
I manage to make it work with one capability. That is, now the CCCS is
stored per capability but I can't enable parallel profiling because
the stacks are still shared.
Now I wanted to have one instance of each stack and cost centre per
capability, so that I can track the behaviour of each cap
Hi again!
I need some help with this.
2010/3/17 Simon Marlow :
> On 16/03/2010 19:34, Henrique Ferreiro wrote:
>>
>> Hello!
>>
>> I am trying to make cost centre profiling work in the threaded rts
>> build in order to use that information to better understand parallel
>> behaviour.
>>
>> Currentl
On 16/03/2010 19:34, Henrique Ferreiro wrote:
Hello!
I am trying to make cost centre profiling work in the threaded rts
build in order to use that information to better understand parallel
behaviour.
Currently I am learning about the internals of GHC and I am thinking
about how this could be do
Hello!
I am trying to make cost centre profiling work in the threaded rts
build in order to use that information to better understand parallel
behaviour.
Currently I am learning about the internals of GHC and I am thinking
about how this could be done. The main blocker is that the current
cost ce
12 matches
Mail list logo
