# L (complexity)

In computational complexity theory, **L** (also known as **LSPACE**, **LOGSPACE** or **DLOGSPACE**) is the complexity class containing decision problems that can be solved by a deterministic Turing machine using a logarithmic amount of writable memory space.^{[1]}^{[2]} Formally, the Turing machine has two tapes, one of which encodes the input and can only be read,^{[3]} whereas the other tape has logarithmic size but can be read as well as written. Logarithmic space is sufficient to hold a constant number of pointers into the input^{[1]} and a logarithmic number of boolean flags, and many basic logspace algorithms use the memory in this way.

## Complete problems and logical characterization

[edit]Every non-trivial problem in **L** is complete under log-space reductions,^{[4]} so weaker reductions are required to identify meaningful notions of **L**-completeness, the most common being first-order reductions.

A 2004 result by Omer Reingold shows that USTCON, the problem of whether there exists a path between two vertices in a given undirected graph, is in **L**, showing that **L** = **SL**, since USTCON is **SL**-complete.^{[5]}

One consequence of this is a simple logical characterization of **L**: it contains precisely those languages expressible in first-order logic with an added commutative transitive closure operator (in graph theoretical terms, this turns every connected component into a clique). This result has application to database query languages: *data complexity* of a query is defined as the complexity of answering a fixed query considering the data size as the variable input. For this measure, queries against relational databases with complete information (having no notion of nulls) as expressed for instance in relational algebra are in **L**.

## Related complexity classes

[edit]**L** is a subclass of **NL**, which is the class of languages decidable in logarithmic space on a nondeterministic Turing machine. A problem in **NL** may be transformed into a problem of reachability in a directed graph representing states and state transitions of the nondeterministic machine, and the logarithmic space bound implies that this graph has a polynomial number of vertices and edges, from which it follows that **NL** is contained in the complexity class **P** of problems solvable in deterministic polynomial time.^{[6]} Thus **L** ⊆ **NL** ⊆ **P**. The inclusion of **L** into **P** can also be proved more directly: a decider using *O*(log *n*) space cannot use more than 2^{O(log n)} = *n*^{O(1)} time, because this is the total number of possible configurations.

**L** further relates to the class **NC** in the following way:
**NC**^{1} ⊆ **L** ⊆ **NL** ⊆ **NC**^{2}.
In words, given a parallel computer *C* with a polynomial number *O*(*n*^{k}) of processors for some constant *k*, any problem that can be solved on *C* in *O*(log *n*) time is in **L**, and any problem in **L** can be solved in *O*(log^{2} *n*) time on *C*.

Important open problems include whether **L** = **P**,^{[2]} and whether **L** = **NL**.^{[7]} It is not even known whether **L** = **NP**.^{[8]}

The related class of function problems is **FL**. **FL** is often used to define logspace reductions.

## Additional properties

[edit]**L** is low for itself, because it can simulate log-space oracle queries (roughly speaking, "function calls which use log space") in log space, reusing the same space for each query.

## Other uses

[edit]The main idea of logspace is that one can store a polynomial-magnitude number in logspace and use it to remember pointers to a position of the input.

The logspace class is therefore useful to model computation where the input is too big to fit in the RAM of a computer. Long DNA sequences and databases are good examples of problems where only a constant part of the input will be in RAM at a given time and where we have pointers to compute the next part of the input to inspect, thus using only logarithmic memory.

## See also

[edit]- L/poly, a nonuniform variant of L that captures the complexity of polynomial-size branching programs

## Notes

[edit]- ^
^{a}^{b}Sipser (1997), p. 295, Definition 8.12 - ^
^{a}^{b}Garey & Johnson (1979), p. 177 **^**On a read/write input tape, a linear amount of memory could be obtained by packing of symbols (as in the proof of the linear speedup theorem), thus evading the logspace contraint.**^**See Garey & Johnson (1979), p. 179, Theorem 7.13 (claim 2)**^**Reingold, Omer (2005).*Undirected ST-connectivity in log-space*. STOC'05: Proceedings of the 37th Annual ACM Symposium on Theory of Computing. ACM, New York. pp. 376–385. doi:10.1145/1060590.1060647. MR 2181639. ECCC TR04-094.**^**Sipser (1997), Corollary 8.21, p. 299.**^**Sipser (1997), p. 297; Garey & Johnson (1979), p. 180**^**"Complexity theory - is it possible that L = NP".

## References

[edit]- Arora, Sanjeev; Barak, Boaz (2009).
*Computational complexity. A modern approach*. Cambridge University Press. ISBN 978-0-521-42426-4. Zbl 1193.68112. - Papadimitriou, Christos (1993).
*Computational Complexity*(1st ed.). Addison Wesley. Chapter 16: Logarithmic space, pp. 395–408. ISBN 0-201-53082-1. - Sipser, Michael (1997).
*Introduction to the Theory of Computation*. PWS Publishing. Section 8.4: The Classes L and NL, pp. 294–296. ISBN 0-534-94728-X. - Garey, M.R.; Johnson, D.S. (1979).
*Computers and Intractability: A Guide to the Theory of NP-Completeness*. W.H. Freeman. Section 7.5: Logarithmic Space, pp. 177–181. ISBN 0-7167-1045-5. MR 0519066. OCLC 247570676. - Cook, Stephen A.; McKenzie, Pierre (1987). "Problems Complete for Deterministic Logarithmic Space" (PDF).
*Journal of Algorithms*.**8**(3): 385–394. doi:10.1016/0196-6774(87)90018-6. ISSN 0196-6774.