Fall 2018 SPO600 Weekly Schedule

This is the schedule and main index page for the SPO600 Software Portability and Optimization course for Fall 2018.

It's Alive!
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.

Week	Week of...	Class I Monday 5:10-6:55 Room S2173	Class II Wednesday 5:10-6:55 Room S2173	Deliverables (Summary - click for details)
1	Sep 3	Labour day	Introduction / Computer architecture overview / How is code accepted into an open source project? (Lab 1)	Set up accounts.
2	Sep 10	Sysadmin for Devs / Building Software (Lab 2)	Compiled C Lab (Lab 3) / Baseline Builds and Benchmarking	Blog your conclusion to Labs 1, 2, and 3.
3	Sep 17	Investigation: Baseline builds		Blog about your baseline builds and benchmarking.
4	Sep 24	Assembly Lab (Lab 4)	Assembly Lab (Lab 4) Continued	Blog your Lab 4 results.
5	Oct 1	(Assembler lab wrap-up)	Compiler Optimizations (Lab 5)	Blog the conclusion to Lab 5.
6	Oct 8	Thanksgiving	Investigation: Impact of Compiler Optimizations	Blog about the impact of compiler optimizations and about your project.
7	Oct 15	Algorithm Selection (Lab 6)	Profiling (Lab 7)	Blog your conclusions to Lab 6 and 7, blog about your project.
	Oct 22	Reading Week and FSOSS 2018
8	Oct 29	SIMD and Auto-vectorization (Lab 8)	Inline assembler (Lab 9)	Blog your conclusions to Lab 8 and 9, blog about your project.
9	Nov 5	Memory	Atomics	Blog about your project.
10	Nov 12	Project Hacking	Compiler Intrinsics	Blog about your project.
11	Nov 19	Project Hacking	Project Hacking	Blog about your project.
12	Nov 26	Project Hacking	Project Hacking	Blog about your project.
13	Dec 3	Project Hacking	Wrap-up Discussion	Blog about your project.
Exam	Dec 10	Exam Week - No exam in this course!

Evaluation

Category	Percentage	Evaluation Dates
Communication	20%	January (blog posts up to Feb 4, 5%), End of February (March 4, 5%), End of March (April 2, 5%), end of course (April 22, 5%).
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 April 21, but it is best if you stay on top of the labs and submit according to the table above.
Project work	60%	3 stages: 15% (March 18), 20% (April 10), 25% (April 22).

Week 1

• Labour day - no Class I this week

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 architecture-specific high-level code or in Assembly Language.
• Reasons that code is architecture-specific:
  • System assumptions that don't hold true on other platforms
    • Variable or word size
    • Endianness
  • Code that takes advantage of platform-specific features
• 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. There is no opportunity to re-take a missed quiz, but your lowest three quiz scores will not be counted, so do not worry if you miss one or two.
  • Students with test accommodations: an alternate monthly quiz is available in the Test Centre. See the professor for details.
• 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.

Course and Setup: Accounts, agreements, servers, and more

• SPO600 Communication Tools
• Winter 2018 SPO600 Participants page
• Key generation for SSH to the SPO600 Servers.
• Student Agreement

How open source communities work

• Code Review Lab (Lab 1) as homework.

Computer Architecture

• 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

Reference

• Computer Architecture and Computer Architecture Category

Week 1 Deliverables

1. Course setup:
   1. Set up your SPO600 Communication Tools - in particular, set up a blog and add it to Planet CDOT (via the Planet CDOT Feed List).
   2. Add yourself to the SPO600 Participants page (leave the projects columns blank).
   3. Generate a pair of keys for SSH and email the public key to your professor, so that he can set up your access to the class servers.
2. Optional (strongly recommended): Set up a personal Fedora system.
3. Optional: Purchase an AArch64 development board (such as a 96Boards HiKey or Raspberry Pi 3. If you use a Pi, install a 64-bit Linux operating system on it, not a 32-bit version).