The problem
A computer can erase its scratch work and reuse the same memory while trying many possibilities. With three on/off switches, it can inspect all eight settings one at a time, storing only the current setting and enough scratch work to check it. More switches make the search much longer without requiring a record of every setting. P versus PSPACE asks whether reusing a moderate amount of memory can solve any decision problem that every moderate-time algorithm fails to solve. Here moderate means bounded by a fixed power of the input length, such as its square or cube; this is a polynomial bound.[1] [3]
Can limited scratch memory, reused over a long computation, decide more problems than a polynomial number of steps? The classes P and PSPACE formalize this question for ordinary deterministic Turing machines. With input length , a polynomial bound has the form for some fixed constant that may depend on the problem. P imposes such a bound on time; PSPACE imposes it on working storage. For example, enumerating the assignments of Boolean variables needs only one -bit assignment counter plus checking workspace, not all assignments stored together. Every polynomial-time computation uses at most polynomial space, so . The open question is whether this containment is strict.[1] [3]
Scope
For ordinary deterministic decision languages on standard Turing-machine models, is P strictly contained in PSPACE, where time or work space is bounded by a polynomial in input length?
What remains open
Separating these classes requires one polynomial-space decision problem with no polynomial-time algorithm, excluding every fixed time exponent. Williams’s 2025 square-root-space simulation yields near-quadratic time lower bounds for certain space-bounded problems, an important narrower result that leaves larger polynomial time bounds possible. A machine given a special external answer source operates in an oracle model; separations there do not by themselves settle ordinary computation.[1] [2] [3]
Why it matters
Memory and time place different limits on what a computer can do. A search may fit in memory but take far too long to finish. Understanding whether this difference is unavoidable for some problems would explain whether abundant patience can compensate for limited working storage in a way that no faster algorithm can match. A slow search alone does not prove such a limit.[1] [3]
Fully quantified Boolean formulas encode a succession of choices, some asking whether a successful option exists and others requiring success for every option. They can be evaluated by exploring branches and retaining only the current branch and intermediate answers; this problem is PSPACE-complete. A polynomial-time algorithm for it would put all PSPACE problems in P. The connection makes the time–space question concrete: can the effort of evaluating all these dependent choices always be avoided while still returning the right answer?[1] [3]
Definitions
3 terms
working storage
Scratch memory occupied during a computation. Space measures the largest amount used at once, so erased memory can be reused rather than charged again.[3]
polynomial bound
A bound , where is input length and is a fixed constant independent of the input. Different problems can have different constants.[3]
PSPACE
Decision problems solvable by a deterministic algorithm using polynomial working space. Their computation time need not be polynomial.[3]
Sources
- Simulating Time With Square-Root Space
Notes on Simulating Time With Square-Root Space
The exact February 25, 2025 version’s introduction, simulation theorem and lower-bound corollaries distinguish near-quadratic time exclusions from the full P versus PSPACE question on multitape Turing machines.
- Mathematics of the Impossible: The Complexity of Computation
Notes on Mathematics of the Impossible: The Complexity of Computation
Existing June 2026 draft locator retained. Fresh direct reads returned a fetch error/403; only an indexed primary preview was accessible. The newly added Arora–Barak draft and Williams introduction provide the actually read time/space definitions and bounds used in this revision.
- Computational Complexity: A Modern Approach (January 2007 Internet draft)
Notes on Computational Complexity: A Modern Approach (January 2007 Internet draft)
Selected Chapter 4 definitions, reusable-workspace example and quantified-formula completeness/branch evaluation passages. January 2007 Internet draft, not the final 2009 edition; no current status certification from this old draft.