Solution

ID: past-exam-of-the-optimisation-for-data-science-course-of-the-university-of-oxford/2023/3/d/solution

The supporting inequality in part 2(a) bounds below by an affine function plus a positive squared Euclidean norm, making it a coercive function. Its continuity gives a global minimizer , which is unique by strict convexity. Let , and . Here is the block size, so its role differs from the number of component functions in Question 2. Use randomized block coordinate descent with uniformly sampled blocks of size , independently at each update. Sampling uniformly from a fixed partition into equal-sized blocks gives the same calculation, since each coordinate has inclusion probability .
Let be a common upper bound on the block Lipschitz constants. Part (c) permits . With step size , part (a) gives
Summing squared partial derivatives according to their inclusion probabilities,
For a strongly convex function, part 2(a) also yields the strong convexity gradient inequality
Indeed, substitute into the supporting inequality and complete the square in : the expression is at least for every .
Combining the last three estimates gives a contraction in conditional expectation:
By the tower property and repeated application,
An optimization epoch counts coordinate partial derivative evaluations: it comprises block updates or one full gradient update. With sampling with replacement, an optimization epoch is this work measure; it need not visit every coordinate. Consequently the block method needs
to bring the expected objective function gap below , for , up to integer rounding.
For the steepest descent method, use a global Lipschitz gradient constant . Part (c) with the full block permits . The descent lemma with step size , together with the strong convexity gradient inequality, gives
An exact line search along the negative gradient does at least as well in objective function decrease per update. Ignoring its additional work, the resulting epoch complexity is
The common coordinate-based guarantees favour blocks by a factor in epochs. In fact, with the conservative constants and , both methods have the same guaranteed contraction per update, while a block update uses only coordinate partial derivatives.
This compares the bounds justified by the given constants. For a particular objective function, sharper constants give the comparison against ; an actual speedup of is not universal. Computing a block coordinate gradient also need not cost exactly of a full gradient evaluation. The epoch complexity comparison assumes that coordinate partial derivative counts are a useful measure of work, and does not itself establish a wall-clock comparison.

New to topics? Read the docs here!