logo       

Related Msgs: audio.musicbrai...    enbd.general/20...    ietf.idr/2002-0...    java.ant-contri...    gnu.make.genera...    qplus.devel/200...    video.freevo.cv...    os.netbsd.ports...    yellowdog.gener...    xfree86.cvs/200...    search.nutch.us...    freedesktop.xse...    programming.swi...    capabilities.ge...    telephony.pbx.a...    mail.sylpheed.c...    db.firebase.por...    boot-loaders.u-...    recreation.radi...    netbsd.bugs/200...    web.zope.plone....    user-groups.lin...   

RE: Adding a field to StgTSO: msg#00153

Subject: RE: Adding a field to StgTSO
 
> > There's not too many StgMainThreads around, so why do
> > you think there's a perf win (at the cost of adding another
> > word to every TSO)?
> 
> When implementing my bound threads proposal, I'd have to query the 
> MainThread for every TSO that is scheduled.
> How many is "not too many"? There is one for each call-in to the RTS, 
> couldn't that become a problem? I'm just afraid of doing a 
> linear scan 
> each time.
> 
> But no, I'm not absolutely convinced, and I can just do my 
> linear scans 
> for now. If it's indeed a performance problem, we'll find out soon 
> enough.

The alternative which I considered is to hash the thread id to the
StgMainThread*.  But on balance, adding one word to the TSO structure is
simpler and won't make a noticeable difference to performance: TSOs are
usually a minimum 1k anwyay, and we always copy the whole lot during GC
(we shouldn't - I must get around to optimising that sometime).  TSOs
bigger than about 3k are treated as large objects and not copied.

Cheers,
        Simon



Try Searching:
servers, voip, java, networking, microsoft ...
<Prev in Thread] Current Thread [Next in Thread>
Google Custom Search

Home | blog view | USPTO Patent Archive | advertise | OSDir is an inevitable website. super tiny logo