Tamarin:WeeklyUpdates: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
mNo edit summary
No edit summary
Line 10: Line 10:
* join irc.mozilla.org #tamarin for attendence taking and questions
* join irc.mozilla.org #tamarin for attendence taking and questions


= Tamarin Tech Summit, February 1, 2008 =
= 11th March 2008 =
 
* [[Tamarin:WeeklyUpdates/TamarinSummit2008|Agenda]]
 
= 15th January 2008 =


== Attendees ==
== Attendees ==


 
* Steven
* Erik
* Edwin
* Grayden
* Jennifer
* Tom
* Moh
* Moh
* Jason
* Marsha
* Marsha
* Brent
* Some other people from Intel
* Benjamin
* Ed
* Rick
* Steven
* Jeff
* Seo
 
== Announcements ==
 
* Tamarin summit February 1st at Adobe – SF


== Updates ==
== Updates ==
'''Jason (ActionMonkey)'''
* Land ActionMonkey changes to mozilla-central.
* Incremental marking
* Thread safe
* Performance number
* tracking bug:
* mozilla-central is the trunk in hg
'''Steven'''
* TT now building on linux


'''Moh (Vtune)'''
'''Moh (Vtune)'''
* code now works fine despite short period of being broken
* uploaded installation and configuration guide on wiki
* is there an area of performance where we'd like Moh's team to focus? 
** edwin: interpreter
** ACTION: Moh will send steven ##TBD## (readu30?)
** ACTION: Moh will look into some hot loops and provide additional information
*** is this loop related to double-byte characters not being processed efficiently? Steven would need more details to confirm.


* jit profiling api
'''Marsha'''
* step 1
* there are other performance tools available. could other tools be useful?
** account: premier account,
** we're most interested in tuning the interpreter and the generated code.
** request: "JIT profiling API of VTUNE"
** speed is a bigger issue than memory footprint for the interpreter
** contact: Gary Carleton
** what are the upper bounds of footprint?  we are targeting:
* step 2 - shipped with vtune
*** memory: 128K RAM
* step 3 - talk about open source
*** code: 100K


'''Marsha (Instrumentation)'''
'''Edwin (Tamarin-tracing)'''
* Steven is continuing to work on bugs
* Edwin is working on ##TBD## algorithm, which uses interpreter.cpp
* There has been a lot of work on the spec, which is part of why there hasn't been a lot of development recently.


* posted a patch for changes needed to invoke Vtune from TC
'''Grayden'''
* an update is coming
* posted updates to mini-tracing patch
** still slightly crashy but can run about half of the sunspider cases now -- getting better!
* ACTION: Edwin will add an updated trace-tree patch to bugzilla later this week (txt patch is fine)
* Steven suggests rebuilding with superwords turned off; this might inprove things.




== Summit Topics ==
= Tamarin Tech Summit, February 1, 2008 =
 
 
* Vtune profiling
* Code walkthrough of the JIT - what optimizations are applied (or not applied)


* [[Tamarin:WeeklyUpdates/TamarinSummit2008|Agenda]]




= Older meetings =
= Older meetings =


* [[Tamarin:WeeklyUpdates/2008-01-08|March 11, 2008]]
* [[Tamarin:WeeklyUpdates/2008-01-08|January 08, 2008]]
* [[Tamarin:WeeklyUpdates/2008-01-08|January 08, 2008]]
* [[Tamarin:WeeklyUpdates/2007-12-18|December 18, 2007]]
* [[Tamarin:WeeklyUpdates/2007-12-18|December 18, 2007]]

Revision as of 21:34, 11 March 2008

These updates concern Tamarin and related projects only.

Meeting Details

  • 2:00pm Pacific Time (21:00 UTC) on Tuesdays
    • (5PM Eastern US, 11PM Oslo, 6AM (Wed) Seoul, 7AM (Wed) Melbourne)
  • Location: Tel: 866 705 2554 (us), 913 227 1201 (int’l)
    • Passcode: 9140087
  • Duration: 60 minutes
  • join irc.mozilla.org #tamarin for attendence taking and questions

11th March 2008

Attendees

  • Steven
  • Edwin
  • Grayden
  • Jennifer
  • Tom
  • Moh
  • Marsha
  • Some other people from Intel

Updates

Moh (Vtune)

  • code now works fine despite short period of being broken
  • uploaded installation and configuration guide on wiki
  • is there an area of performance where we'd like Moh's team to focus?
    • edwin: interpreter
    • ACTION: Moh will send steven ##TBD## (readu30?)
    • ACTION: Moh will look into some hot loops and provide additional information
      • is this loop related to double-byte characters not being processed efficiently? Steven would need more details to confirm.

Marsha

  • there are other performance tools available. could other tools be useful?
    • we're most interested in tuning the interpreter and the generated code.
    • speed is a bigger issue than memory footprint for the interpreter
    • what are the upper bounds of footprint? we are targeting:
      • memory: 128K RAM
      • code: 100K

Edwin (Tamarin-tracing)

  • Steven is continuing to work on bugs
  • Edwin is working on ##TBD## algorithm, which uses interpreter.cpp
  • There has been a lot of work on the spec, which is part of why there hasn't been a lot of development recently.

Grayden

  • posted updates to mini-tracing patch
    • still slightly crashy but can run about half of the sunspider cases now -- getting better!
  • ACTION: Edwin will add an updated trace-tree patch to bugzilla later this week (txt patch is fine)
  • Steven suggests rebuilding with superwords turned off; this might inprove things.


Tamarin Tech Summit, February 1, 2008


Older meetings

Retrieved from "https://wiki.allizom.org/index.php?title=Tamarin:WeeklyUpdates&oldid=86348"