Difference between revisions of "Fall 2021 SPO600 Weekly Schedule"

From CDOT Wiki
Jump to: navigation, search
(Created page with "Category:Fall 2021 SPO600 This is the schedule and main index page for the SPO600 ''Software Portability and Optimization'' course for Fall 2021. <!-- {{Admon/importan...")
 
Line 1: Line 1:
 
[[Category:Fall 2021 SPO600]]
 
[[Category:Fall 2021 SPO600]]
 
This is the schedule and main index page for the [[SPO600]] ''Software Portability and Optimization'' course for Fall 2021.
 
This is the schedule and main index page for the [[SPO600]] ''Software Portability and Optimization'' course for Fall 2021.
<!-- {{Admon/important|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.}} -->
+
{{Admon/important|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.}}
{{Admon/important|Content being Updated|This page is in the process of being updated from a previous semester's content. It is not yet updated for the current semester. Do not rely on the accuracy of this information until this warning is removed.}}
+
<!-- {{Admon/important|Content being Updated|This page is in the process of being updated from a previous semester's content. It is not yet updated for the current semester. Do not rely on the accuracy of this information until this warning is removed.}} -->
 
<!-- {{Admon/obsolete|[[Current SPO600 Weekly Schedule]]}} -->
 
<!-- {{Admon/obsolete|[[Current SPO600 Weekly Schedule]]}} -->
  
Line 14: Line 14:
 
|-
 
|-
  
|1||Jan 06||[[#Week 1 - Class I|Introduction to the Course / Introduction to the Problem / How is code accepted into an open source project? (Homework: Lab 1)]]||[[#Week 1 - Class II|Computer architecture basics / Binary Representation of Data / Introduction to Assembly Language]]||[[#Week 1 Deliverables|Set up for the course]]
+
|1||Sep 7||style="background:#f0f0ff"|Labour Day Holiday||[[#Week 1 - Class II|Introduction to the Course / Introduction to the Problem / How is code accepted into an open source project?]]||[[#Week 1 Deliverables|Set up for the course / Lab 1]]
 
|-
 
|-
|2||Jan 13||[[#Week 2 - Class I|6502 Assembly Basics Lab (Lab 2)]]||[[#Week 2 - Class II|Math, Assembly language conventions, and Examples]]||[[#Week 2 Deliverables|Lab 1 and 2]]
+
|2||Sep 13||[[#Week 2 - Class I|Binary Representation of Data / Computer architecture basics / Introduction to Assembly Language]]||[[#Week 2 - Class II|6502 Assembly Basics Lab (Lab 2)]]||[[#Week 2 Deliverables|Lab 2]]
 
|-
 
|-
|3||Jan 20||[[#Week 3 - Class I|6502 Math Lab (Lab 3)]]||[[#Week 3 - Class II|Addressing Modes]]||[[#Week 3 Deliverables|Lab 3]]
+
|3||Sep 20||[[#Week 3 - Class I|Math, Assembly language contentions, and Examples]]||[[#Week 3 - Class II|6502 Math Lab (Lab 2)]]||[[#Week 3 Deliverables|Lab 3]]
 
|-
 
|-
|4||Jan 27||[[#Week 4 - Class I|Continue with Lab 3]]||[[#Week 4 - Class II|System routines / Building Code]]||[[#Week 4 Deliverables|Lab 3]]
+
|4||Sep 27||[[#Week 4 - Class I|Addressing Modes]]||[[#Week 4 - Class II|6502 Assembler (Cont'd)]]||[[#Week 4 Deliverables|September Blog Posts]]
 
|-
 
|-
|5||Feb 03||[[#Week 5 - Class I|6502 String Lab (Lab 4)]]||[[#Week 5 - Class II|Introduction to x86_64 and AArch64 architectures]]||[[#Week 5 Deliverables|Lab 4]]
+
|5||Oct 4||[[#Week 5 - Class I|System Routines / Strings / Building Code]]||[[#Week 5 - Class II|6502 String Lab (Lab 4)]]||[[#Week 5 Deliverables|Lab 4]]
 
|-
 
|-
|6||Feb 10||[[#Week 6 - Class I|6502 String Lab (Lab 4) Continued]]||[[#Week 6 - Class II|x86_64 and AArch64 Assembly]]||[[#Week 6 Deliverables|Lab 4]]
+
|6||Oct 12||style="background:#f0f0ff"|[[#Week 6 - Class I|Thanksgiving Holiday]]||[[#Week 6 - Class II|x86_64 and AArch64 Assembly]]||[[#Week 6 Deliverables|Lab 5]]
 
|-
 
|-
|7||Feb 17||style="background:#f0f0ff"|Family Day Holiday||[[#Week 7 - Class II|64-bit Assembly Language Lab (Lab 5)]]||[[#Week 7 Deliverables|Lab 5]]
+
|7||Oct 18||x86_64 and AArch64 Assembly / Compiler Optimiations / Project Selection||[[#Week 7 - Class II|Completion Lab (Lab 6)]]||[[#Week 7 Deliverables|Lab 6]]
 
|-
 
|-
|Reading||Feb 24||style="background: #f0f0ff" colspan="5" align="center"|Reading Week
+
|Reading||Oct 25||style="background: #f0f0ff" colspan="5" align="center"|Reading Week
 
|-
 
|-
|8||Mar 02||[[#Week 8 - Class I|Lab 5 Continued]]||[[#Week 8 - Class II|Projects / Changing an Algorithm]]||[[#Week 8 Deliverables|Lab 5, Project Blogs]]
+
|8||Nov 1||[[#Week 8 - Class I|Profiling]]||[[#Week 8 - Class II|Profiling Lab (Lab 7)]]||[[#Week 8 Deliverables|October Blog Posts / Project Stage 1]]
 
|-
 
|-
|9||Mar 09||[[#Week 9 - Class I|Algorithm Selection Lab (Lab 6)]]||[[#Week 9 - Class II|Compiler Optimizations / SIMD and Vectorization]]||[[#Week 9 Deliverables|Lab 6]]
+
|9||Nov 8||[[#Week 9 - Class I|Optimization through Algorithm Selection]]||[[#Week 9 - Class II|Compilation Lab (Lab 6)]]||[[#Week 9 Deliverables|Lab 6]]
 
|-
 
|-
|Switchover||Mar 16||style="background: #f0f0ff" colspan="5" align="center"|Online Switchover Week
+
|10||Nov 15||[[#Week 10 - Class I|Single Instruction, Multiple Data (SIMD) and Vectorization]]||[[#Week 10 - Class II|SIMD and Vectorization Lab (Lab 8)]]||[[#Week 10 Deliverables|Lab 8]]
 
|-
 
|-
|10||Mar 23||[[#Week 10 - Class I|Online Startup / Project Stage 1]]||[[#Week 10 - Class II|Review for Stage 1]]||[[#Week 10 Deliverables|Project Blogging]]
+
|11||Nov 22||[[#Week 11 - Class I|Intrinsics and inline Assembler]]||[[#Week 11 - Class II|Intrinsics Lab (Lab 9)]]||[[#Week 11 Deliverables|Project Stage 2]]
 
|-
 
|-
|11||Mar 30||[[#Week 11 - Class I|<span style="background: #ffff00;">Quiz</span> / Profiling]]||[[#Week 11 - Class II|SIMD Part 1 - Autovectorization]]||[[#Week 11 Deliverables|Project Stage 1 due April 1, 11:59 pm / Blog about your project as you start Stage 2]]
+
|12||Nov 29||[[#Week 12 - Class I|Project Discussion]]||[[#Week 12 - Class II|Project Discussion]]||[[#Week 12 Deliverables|Lab 9 / November Blog Posts]]
 
|-
 
|-
|12||Apr 06||[[#Week 12 - Class I|SIMD Part 2 - Intrinsics and Inline Assembler]]||style="background:#f0f0ff"|Good Friday Holiday||[[#Week 12 Deliverables|Project Stage 2 due]]
+
|13||Dec 6||[[#Week 13 - Class I|Project Discussion]]||[[#Week 13 - Class II|Lab 10]]||[[#Week 13 Deliverables|Lab 10]]
 
|-
 
|-
|13||Apr 13||[[#Week 13 - Class I|<span style="background: #ffff00;">Quiz</span> / Project Discussion]]||[[#Week 13 - Class II|Wrap-up Discussion]]||[[#Week 13 Deliverables|Project Stage 3 due Monday, April 20, 11:59 pm (Firm!)]]
+
|14||Dec 13||[[#Week 13 - Class I|Future Directions in Architecture]]||[[#Week 13 - Class II|Wrap-up Discussion]]||[[#Week 13 Deliverables|December Blog Posts / Project Stage 3]]
 
|-
 
|-
 
|}
 
|}
Line 48: Line 48:
 
== Week 1 ==
 
== Week 1 ==
  
=== Week 1 - Class I ===
+
=== Week 1 - Class II ===
  
 
==== Introduction to the Problems ====
 
==== Introduction to the Problems ====

Revision as of 13:53, 1 September 2021

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

Important.png
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
Tuesday 1:30-3:15
Room B1024
Class II
Friday 11:40-1:25
Room K1263
Deliverables
(Summary - click for details)
1 Sep 7 Labour Day Holiday Introduction to the Course / Introduction to the Problem / How is code accepted into an open source project? Set up for the course / Lab 1
2 Sep 13 Binary Representation of Data / Computer architecture basics / Introduction to Assembly Language 6502 Assembly Basics Lab (Lab 2) Lab 2
3 Sep 20 Math, Assembly language contentions, and Examples 6502 Math Lab (Lab 2) Lab 3
4 Sep 27 Addressing Modes 6502 Assembler (Cont'd) September Blog Posts
5 Oct 4 System Routines / Strings / Building Code 6502 String Lab (Lab 4) Lab 4
6 Oct 12 Thanksgiving Holiday x86_64 and AArch64 Assembly Lab 5
7 Oct 18 x86_64 and AArch64 Assembly / Compiler Optimiations / Project Selection Completion Lab (Lab 6) Lab 6
Reading Oct 25 Reading Week
8 Nov 1 Profiling Profiling Lab (Lab 7) October Blog Posts / Project Stage 1
9 Nov 8 Optimization through Algorithm Selection Compilation Lab (Lab 6) Lab 6
10 Nov 15 Single Instruction, Multiple Data (SIMD) and Vectorization SIMD and Vectorization Lab (Lab 8) Lab 8
11 Nov 22 Intrinsics and inline Assembler Intrinsics Lab (Lab 9) Project Stage 2
12 Nov 29 Project Discussion Project Discussion Lab 9 / November Blog Posts
13 Dec 6 Project Discussion Lab 10 Lab 10
14 Dec 13 Future Directions in Architecture Wrap-up Discussion December Blog Posts / Project Stage 3

Week 1

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
    • 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 https://wiki.cdot.senecacollege.ca/wiki/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)
  • 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

How open source communities work