Athena MP Shared Reader Developments Peter van Gemmeren

  • Slides: 3
Download presentation
Athena. MP Shared. Reader Developments Peter van Gemmeren

Athena. MP Shared. Reader Developments Peter van Gemmeren

Shared. Reader § § § Shared. Readed for Athena. MP In addition to sharing

Shared. Reader § § § Shared. Readed for Athena. MP In addition to sharing event Token when iterating, the shared reader can share POOL objects on demand. Single Shared. Reader Process, uses two separate instances of the Athena. Shared. Memory. Tool: 1. Event Token sharing between Event. Selector • Existed for some time, easier as iteration is predictable by the server and Tokens are simple strings. 2. Data Object sharing between Conversion. Svc • § New prototype, allows on demand read of objects serialized by Athena. Serialization. Tool t(currently implemented using ROOT only At this point, uses shared memory, but could be implemented in Yampl as well. Go to ”Insert (View) | Header and Footer" to add your organization, sponsor, meeting name here; then, click "Apply to All" 2

Performance and Next Steps § § § Intended to work for simulation, which uses

Performance and Next Steps § § § Intended to work for simulation, which uses few container per event. Initially found a performance penalty of ~30%, ouch, but functionality seems ok. Now, after some improvements, performance seems similar to default Athena. MP: – There are still a few loose ends to fix • E. g. : Currently Athena. MP calls Read. Events(max. Evt) several times, but with the object reader this will not work… – This hasn’t been tested yet § § So far tested only with local file access Single reader may have advantages for caching (more memory, all the cache is used), but also may lead to complications (e. g. : cache swapping on boundaries). Go to ”Insert (View) | Header and Footer" to add your organization, sponsor, meeting name here; then, click "Apply to All" 3