Difference between revisions of "Fall 2017 SPO600 Weekly Schedule"
Chris Tyler (talk | contribs) |
Chris Tyler (talk | contribs) |
||
| Line 74: | Line 74: | ||
|Project work||align="right"|60%||3 stages: 15% (Oct 20) / 20% (Nov 17) / 25% (Dec 8) | |Project work||align="right"|60%||3 stages: 15% (Oct 20) / 20% (Nov 17) / 25% (Dec 8) | ||
|} | |} | ||
| + | |||
== Week 1 == | == Week 1 == | ||
There is no "Class I" during this first week due to Labour Day. | There is no "Class I" during this first week due to Labour Day. | ||
| + | |||
=== Week 1 - Class II === | === Week 1 - Class II === | ||
| Line 149: | Line 151: | ||
== Week 2 == | == Week 2 == | ||
| + | |||
=== Week 2 - Class I === | === Week 2 - Class I === | ||
| Line 158: | Line 161: | ||
** ELF | ** ELF | ||
** Procedure calling conventions | ** Procedure calling conventions | ||
| + | |||
=== Week 2 - Class II === | === Week 2 - Class II === | ||
| Line 190: | Line 194: | ||
* [[SPO600 Code Building Lab|Code Building Lab (Lab 2)]] as homework | * [[SPO600 Code Building Lab|Code Building Lab (Lab 2)]] as homework | ||
| + | |||
=== Week 2 Deliverables === | === Week 2 Deliverables === | ||
Revision as of 08:24, 10 September 2017
This is the schedule and main index page for the SPO600 Software Portability and Optimization course for Winter 2017.
This SPO600 weekly schedule will be updated as the course proceeds - dates and content are subject to change. The cells in the summary table will be linked to relevant resources and labs as the course progresses.
Schedule Summary Table
This is a summary/index table. Please follow the links in each cell for additional detail which will be added below as the course proceeds -- especially for the Deliverables column.
Evaluation
| Category | Percentage | Evaluation Dates |
|---|---|---|
| Communication | 20% | 5% each: End of September, End of Study Week (October 29), November 19, end of course. |
| Quizzes | 10% | May be held during any class, usually at the start of class. A minimum of 5 one-page quizzes will be given. No make-up/retake option is offered if you miss a quiz. Lowest 3 scores will not be counted. |
| Labs | 10% | See deliverables column above. All labs must be submitted by Dec 8. |
| Project work | 60% | 3 stages: 15% (Oct 20) / 20% (Nov 17) / 25% (Dec 8) |
Week 1
There is no "Class I" during this first week due to Labour Day.
Week 1 - Class II
Introduction to the Problems
Porting and Portability
- Most software is written in a high-level language which can be compiled into machine code for a specific computer architecture. In many cases, this code can be compiled for multiple architectures. However, there is a lot of existing code that contains some architecture-specific code fragments written in Assembly Language (or, in some cases, machine-specific high-level code).
- Reasons for writing code in Assembly Langauge include:
- Performance
- Atomic Operations
- Direct access to hardware features, e.g., CPUID registers
- Most of the historical reasons for including assembler are no longer valid. Modern compilers can out-perform most hand-optimized assembly code, atomic operations can be handled by libraries or compiler intrinsics, and most hardware access should be performed through the operating system or appropriate libraries.
- A new architecture has appeared: AArch64, which is part of ARMv8. This is the first new computer architecture to appear in several years (at least, the first mainstream computer architecture).
- At this point, most key open source software (the software typically present in a Linux distribution such as Ubuntu or Fedora, for example) now runs on AArch64. However, it may not run as well as on older architectures (such as x86_64).
Benchmarking and Profiling
Benchmarking involves testing software performance under controlled conditions so that the performance can be compared to other software, the same software operating on other types of computers, or so that the impact of a change to the software can be gauged.
Profiling is the process of analyzing software performance on finer scale, determining resource usage per program part (typically per function/method). This can identify software bottlenecks and potential targets for optimization.
Optimization
Optimization is the process of evaluating different ways that software can be written or built and selecting the option that has the best performance tradeoffs.
Optimization may involve substituting software algorithms, altering the sequence of operations, using architecture-specific code, or altering the build process. It is important to ensure that the optimized software produces correct results and does not cause an unacceptable performance regression for other use-cases, system configurations, operating systems, or architectures.
The definition of "performance" varies according to the target system and the operating goals. For example, in some contexts, low memory or storage usage is important; in other cases, fast operation; and in other cases, low CPU utilization or long battery life may be the most important factor. It is often possible to trade off performance in one area for another; using a lookup table, for example, can reduce CPU utilization and improve battery life in some algorithms, in return for increased memory consumption.
Most advanced compilers perform some level of optimization, and the options selected for compilation can have a significant effect on the trade-offs made by the compiler, affecting memory usage, execution speed, executable size, power consumption, and debuggability.
Build Process
Building software is a complex task that many developers gloss over. The simple act of compiling a program invokes a process with five or more stages, including pre-proccessing, compiling, optimizing, assembling, and linking. However, a complex software system will have hundreds or even thousands of source files, as well as dozens or hundreds of build configuration options, auto configuration scripts (cmake, autotools), build scripts (such as Makefiles) to coordinate the process, test suites, and more.
The build process varies significantly between software packages. Most software distribution projects (including Linux distributions such as Ubuntu and Fedora) use a packaging system that further wraps the build process in a standardized script format, so that different software packages can be built using a consistent process.
In order to get consistent and comparable benchmark results, you need to ensure that the software is being built in a consistent way. Altering the build process is one way of optimizing software.
Note that the build time for a complex package can range up to hours or even days!
General Course Information
- Course resources are linked from the CDOT wiki, starting at http://wiki.cdot.senecacollege.ca/wiki/index.php/SPO600 (Quick find: This page will usually be Google's top result for a search on "SPO600").
- Coursework is submitted by blogging.
- Quizzes will be short (1 page) and will be held without announcement at any time, generally at the start of class. Your lowest three quiz scores will not be counted, so do not worry if you miss one or two.
- Course marks (see Weekly Schedule for dates):
- 60% - Project Deliverables
- 20% - Communication (Blog and Wiki writing)
- 20% - Labs and Quizzes (10% labs - completed/not completed; 10% for quizzes - lowest 3 scores not counted)
- All classes will be held in an Active Learning Classroom -- you are encouraged to bring your own laptop to class. If you do not have a laptop, consider signing one out of the Learning Commons for class, or using a smartphone with an HDMI adapter.
- For more course information, refer to the SPO600 Weekly Schedule (this page), the Course Outline, and SPO600 Course Policies.
Discussion of how open source communities work
- Background for the Code Review Lab (Lab 1).
Week 1 Deliverables
- Course setup:
- Set up your SPO600 Communication Tools - in particular, set up a blog and add it to Planet CDOT (via the Planet CDOT Feed List).
- Add yourself to the Fall 2017 SPO600 Participants page (leave the projects columns blank).
- Generate a pair of keys for SSH and email the public key to your professor.
- Sign and return the Open Source Professional Option Student Agreement.
- Complete Labs
- Code Review Lab (Lab 1) (Due end of week 2)
- Optional (recommended): Set up a personal Fedora system.
- Optional: Purchase an AArch64 development board (such as a 96Boards HiKey or Raspberry Pi 2/3).
Week 2
Week 2 - Class I
- Computer Architecture overview (see also the Computer Architecture Category)
- A first look at the x86_64 and AArch64 Architectures and ISA
- Register file comparison
- Instruction encoding
- ELF
- Procedure calling conventions
Week 2 - Class II
- Overview of the Build and Release Process
- Working with Code
- Getting Code
- In a tarball
- From git
- Git basics
- Working with other version control systems
- Getting and Installing Build Dependencies
- Required tools
- Required libraries, headers, and modules
- Building the Code
- Configuration tools (autotools, cmake)
- Make
- The compiler toolchain
- Preprocessor
- Compiler
- Assembler
- Linker
- Debug vs. Non-debug/Stripped binaries
- Installation Scripts
- Getting Code
- Looking at How Distributions Package the Code
- Using fedpkg
- How do you Test without Compromising the Running System?
- Paths
- glibc
- Code Building Lab (Lab 2) as homework
Week 2 Deliverables
- Blog your conclusion to the Code Review Lab (Lab 1)
- Blog the results and conclusion from the Code Building Lab (Lab 2)
