PPO
Proximal Policy Optimization, or PPO, inherits TRPO's principle: improve performance without drifting too far. But instead of solving a KL-constrained optimization problem, PPO directly flattens the objective when updates get too large.
That flattening prevents the policy from over-correcting on a single batch. Conceptually, clipping means: do not get too excited about one lucky game.
Equation walkthrough
PPO flattens the objective when updates get too large
Click each term to see how the clipped surrogate objective mimics TRPO's trust-region idea without solving a constrained optimization problem.
Clip operation
flatten excessive changes
Clipping limits how far the probability ratio can move away from 1, flattening the objective once the update becomes too large.
Terms
The clipped PPO objective is
where
If , the new policy assigns higher probability to that action. If , it assigns lower probability.
The operation limits how far the ratio can move away from , preventing overly large updates. The operator takes the smaller, more conservative improvement between the unclipped and clipped objectives.
The parameter controls the size of this practical trust region: smaller makes learning more cautious, while larger allows bolder updates.
Epsilon lab
Epsilon controls how aggressive PPO is allowed to be
Move the new policy probability and the clipping range. PPO lets useful changes through, then flattens the gradient once the probability ratio leaves the safe region.
rt(θ)
1.44
safe range
0.80-1.20
unclipped
2.88
used by PPO
2.40
Gradient flattened
The action was good, but PPO gives no extra objective gain for pushing its probability this far on the same batch.
PPO clipping
No extra credit for an oversized probability jump
Keep the old probability fixed at 50% and the advantage fixed at At = +2. Choose the new policy's probability for the same sampled action.
What PPO clips
ratio rt
1.6
clipped ratio
1.2
rtAt
3.2
used value
2.4
The min-plus-clip trick mimics TRPO's KL constraint implicitly. PPO still tries to keep updates within a safe policy region, but it does so with a clipped surrogate objective that is much easier to optimize.
If the new policy increases the probability of a good action just a little, great. If it increases that probability too much, PPO clips the gain: no extra reward for extreme changes.
Unlike REINFORCE or simple A2C updates, PPO can reuse the same freshly collected trajectories for several gradient steps. That improves sample efficiency while staying on-policy enough for stable learning.
Why PPO Dominates Modern Pipelines
PPO fits actor-critic architectures easily, handles noisy feedback reasonably well, works with large-batch GPU training, and is comparatively robust to hyperparameters.
That combination matters for later RL pipelines: the method is stable enough to train large policies, simple enough to implement at scale, and flexible enough to tolerate messy advantage estimates.
Epsilon as a Tuning Knob
Small means conservative and stable. Large means more aggressive and exploratory, but riskier. PPO turns a difficult trust-region problem into a simple learning-aggressiveness knob.
In practice, decides how much PPO is allowed to trust one batch before it says: enough, no more extra gain from moving farther.
For a positive advantage , what does PPO clipping do when becomes much larger than ?