Difference between revisions of "Winter 2018 SPO600 Weekly Schedule"

From CDOT Wiki
Jump to: navigation, search
Line 17: Line 17:
 
|-
 
|-
  
|2||Jan 22||[[#Week 2 - Class I|Computer Architecture Overview - Binary representation, processor internals, instruction set architecture]]||[[#Week 2 - Class II|Compiled C Lab (Lab 2)]]<!--  Overview of Working with Code and Building Software - Toolchains, compiler stages, switches and flags, binary file contents (Lab 2)]] -->||[[#Week 2 Deliverables|Blog your conclusion to Labs 1 and 2.]]
+
|2||Jan 22||[[#Week 2 - Class I|Computer Architecture Overview - Binary representation, processor internals, instruction set architecture]]||[[#Week 2 - Class II|Compiled C Lab (Lab 2)]]||[[#Week 2 Deliverables|Blog your conclusion to Labs 1 and 2.]]
 
|-
 
|-
  
Line 125: Line 125:
  
 
=== Week 1 - Class II ===
 
=== Week 1 - Class II ===
 +
 +
==== Course and Setup: Accounts, agreements, servers, and more ====
 +
 +
* [[SPO600 Communication Tools]]
 +
* [[Winter 2018 SPO600 Participants]] page
 +
* [[SPO600_Servers#Preparatory_Steps|Key generation]] for [[SSH]] to the [[SPO600 Servers]].
 +
* Student Agreement
  
 
==== Discussion of how open source communities work ====
 
==== Discussion of how open source communities work ====
Line 138: Line 145:
 
## Generate a [[SPO600_Servers#Preparatory_Steps|pair of keys]] for [[SSH]] and email the public key to your professor, so that he can set up your access to the [[SPO600_Servers class servers]].
 
## Generate a [[SPO600_Servers#Preparatory_Steps|pair of keys]] for [[SSH]] and email the public key to your professor, so that he can set up your access to the [[SPO600_Servers class servers]].
 
## Sign and return the [[Open Source Professional Option Student Agreement]] (this will be done on paper in class).
 
## Sign and return the [[Open Source Professional Option Student Agreement]] (this will be done on paper in class).
# Complete Labs
 
## [[SPO600 Code Review Lab|Code Review Lab (Lab 1)]] (Due end of week 2)
 
 
# Optional (recommended): [[SPO600 Host Setup|Set up a personal Fedora system]].
 
# Optional (recommended): [[SPO600 Host Setup|Set up a personal Fedora system]].
 
# Optional: Purchase an AArch64 development board (such as a [http://96boards.org 96Boards] HiKey or Raspberry Pi 2/3).
 
# Optional: Purchase an AArch64 development board (such as a [http://96boards.org 96Boards] HiKey or Raspberry Pi 2/3).
Line 206: Line 211:
  
 
* [[SPO600 Code Building Lab|Code Building Lab (Lab 2)]] as homework
 
* [[SPO600 Code Building Lab|Code Building Lab (Lab 2)]] as homework
-->
 
 
* [[SPO600 Compiled C Lab|Compiled C Lab (Lab 2)]]
 
* [[SPO600 Compiled C Lab|Compiled C Lab (Lab 2)]]
 
=== Week 2 Deliverables ===
 
=== Week 2 Deliverables ===
Line 470: Line 474:
 
* Blog about your selected function(s) and project plan
 
* Blog about your selected function(s) and project plan
 
** Remember: You should be posting 1-2 times per week
 
** Remember: You should be posting 1-2 times per week
<!--
 
  
 
#################################################################################
 
#################################################################################
Line 645: Line 648:
 
* Complete ALL your blogging for this course by Midnight on Thursday, April 21. Make sure that you have included all of the labs, your presentation, and your project work. Remember that there should be at least 1-2 posts per week. Your blogging from April 1-April 21 will be used for your April communication mark.
 
* Complete ALL your blogging for this course by Midnight on Thursday, April 21. Make sure that you have included all of the labs, your presentation, and your project work. Remember that there should be at least 1-2 posts per week. Your blogging from April 1-April 21 will be used for your April communication mark.
  
-->
+
== Week 2 ==
<!-- == Week 2 ==
 
  
 
=== Tuesday (Sep 15) ===
 
=== Tuesday (Sep 15) ===

Revision as of 16:21, 18 January 2018

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

Important.png
Content being Updated
This page is in the process of being updated from a previous semester's content. It is not yet fully updated for Winter 2018. Do not rely on the accuracy of this information until this warning is removed.

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
Wednesday 3:20-5:05
Room S2174
Class II
Friday 9:50-11:35
Room S2172
Deliverables
(Summary - click for details)
1 Jan 15 Introduction Account setup for this course. / How is code accepted into an open source project? (Lab 1) Set up accounts.
2 Jan 22 Computer Architecture Overview - Binary representation, processor internals, instruction set architecture Compiled C Lab (Lab 2) Blog your conclusion to Labs 1 and 2.
3 Jan 29 Assembly Lab (Lab 3) Assembly Lab (Lab 3 - continued) and Code Bulding Lab (Lab 4) Blog your results and conclusions for Lab 3
4 Feb 5 Compiler Optimizations SIMD and Auto-Vectorization (Lab 5) Blog your Auto-Vectorization Lab (Lab 5) results.
5 Feb 12 Algorithm Selection (Lab 6) Inline Assembler (Lab 7) Blog about your Lab 6 and Lab 7.
6 Feb 19 Project Selection Project: Building, Benchmarking, and Profiling Blog about your project
Feb 26 Reading Week
7 Mar 5 Project Hacking Project Hacking Blog about your project.
8 Mar 12 Project Hacking Project Hacking Blog about your project.
9 Mar 19 Project Hacking Project Hacking Blog about your project.
10 Mar 26 Project Hacking Project Hacking Blog about your project.
11 Apr 2 Project Hacking Project Hacking Blog about your project.
12 Apr 9 Project Hacking Project Hacking Blog about your project.
13 Apr 16 Project Hacking Wrap-up Discussion Blog about your project.

Evaluation

Category Percentage Evaluation Dates
Communication 20% January (5%), End of February (5%), End of March (5%), end of course (April 21 - 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% (date TBA), 20% (date TBA), 25% (April 21).

Week 1

Week 1 - Class I

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.

Week 1 - Class II

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

Discussion of how open source communities work


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 Fall 2017 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 SPO600_Servers class servers.
    4. Sign and return the Open Source Professional Option Student Agreement (this will be done on paper in class).
  2. Optional (recommended): Set up a personal Fedora system.
  3. Optional: Purchase an AArch64 development board (such as a 96Boards HiKey or Raspberry Pi 2/3).