Difference between revisions of "Staff Priorities - Scott"
From SCECpedia
Jump to navigationJump to search| Line 2: | Line 2: | ||
*Looked at Shiyu's volume results, 1D results - emailed out to group | *Looked at Shiyu's volume results, 1D results - emailed out to group | ||
*Submitted TAU profiling run on Kraken | *Submitted TAU profiling run on Kraken | ||
| + | *Submitted 27x weak scaling run on Kraken | ||
*Identified 3.5 TB of SGTs to move to Ranch, started transfer | *Identified 3.5 TB of SGTs to move to Ranch, started transfer | ||
*Continued work on RupGen-api memcached support | *Continued work on RupGen-api memcached support | ||
| Line 7: | Line 8: | ||
== Today == | == Today == | ||
*Ask Shiyu to generate SGTs for volume | *Ask Shiyu to generate SGTs for volume | ||
| − | |||
*Monitor Ranch transfer and md5sums (very slow!) | *Monitor Ranch transfer and md5sums (very slow!) | ||
*Test SGT Merge on Kraken | *Test SGT Merge on Kraken | ||
Revision as of 18:07, 2 March 2012
Yesterday
- Looked at Shiyu's volume results, 1D results - emailed out to group
- Submitted TAU profiling run on Kraken
- Submitted 27x weak scaling run on Kraken
- Identified 3.5 TB of SGTs to move to Ranch, started transfer
- Continued work on RupGen-api memcached support
Today
- Ask Shiyu to generate SGTs for volume
- Monitor Ranch transfer and md5sums (very slow!)
- Test SGT Merge on Kraken
- Continue work on RupGen-api memcached support
Blocked
- No
Follow-ups
- No
Areas of Responsibilities
- CyberShake 1.4
- Broadband CyberShake
- Code migration
