Conditional Lower Bounds for Space/Time Tradeoffs
Isaac Goldstein, Tsvi Kopelowitz, Moshe Lewenstein, Ely Porat

TL;DR
This paper investigates conditional space lower bounds for data structures, revealing that many problems with known polynomial time lower bounds also exhibit space-time tradeoffs, thus deepening understanding of their computational complexity.
Contribution
It introduces a novel framework for polynomial space conjectures, establishing space lower bounds and tradeoffs for well-studied problems based on hardness assumptions.
Findings
Many problems with polynomial time lower bounds also have space hardness.
Tradeoffs between space and query time can be smooth or singular.
Matching upper bounds are presented for several space hardness conjectures.
Abstract
In recent years much effort has been concentrated towards achieving polynomial time lower bounds on algorithms for solving various well-known problems. A useful technique for showing such lower bounds is to prove them conditionally based on well-studied hardness assumptions such as 3SUM, APSP, SETH, etc. This line of research helps to obtain a better understanding of the complexity inside P. A related question asks to prove conditional space lower bounds on data structures that are constructed to solve certain algorithmic tasks after an initial preprocessing stage. This question received little attention in previous research even though it has potential strong impact. In this paper we address this question and show that surprisingly many of the well-studied hard problems that are known to have conditional polynomial time lower bounds are also hard when concerning space. This…
Peer Reviews
No public reviews on file for this paper yet. If you reviewed it on a platform where reviews are public (OpenReview, ICLR, NeurIPS, ICML), you can paste yours below so the community can read it here.
Videos
No videos yet. Explain this paper in a talk, walkthrough, or lecture? Add one.
11affiliationtext: Bar-Ilan University
{goldshi,moshe,porately}@cs.biu.ac.il22affiliationtext: University of Waterloo
Conditional Lower Bounds for Space/Time Tradeoffs
Isaac Goldstein This research is supported by the Adams Foundation of the Israel Academy of Sciences and Humanities
Tsvi Kopelowitz Part of this work took place while the second author was at University of Michigan. This work is supported in part by the Canada Research Chair for Algorithm Design, NSF grants CCF-1217338, CNS-1318294, and CCF-1514383
Moshe Lewenstein This work was partially supported by an ISF grant #1278/16
Ely Porat ††footnotemark:
Abstract
In recent years much effort has been concentrated towards achieving polynomial time lower bounds on algorithms for solving various well-known problems. A useful technique for showing such lower bounds is to prove them conditionally based on well-studied hardness assumptions such as 3SUM, APSP, SETH, etc. This line of research helps to obtain a better understanding of the complexity inside P.
A related question asks to prove conditional space lower bounds on data structures that are constructed to solve certain algorithmic tasks after an initial preprocessing stage. This question received little attention in previous research even though it has potential strong impact.
In this paper we address this question and show that surprisingly many of the well-studied hard problems that are known to have conditional polynomial time lower bounds are also hard when concerning space. This hardness is shown as a tradeoff between the space consumed by the data structure and the time needed to answer queries. The tradeoff may be either smooth or admit one or more singularity points.
We reveal interesting connections between different space hardness conjectures and present matching upper bounds. We also apply these hardness conjectures to both static and dynamic problems and prove their conditional space hardness.
We believe that this novel framework of polynomial space conjectures can play an important role in expressing polynomial space lower bounds of many important algorithmic problems. Moreover, it seems that it can also help in achieving a better understanding of the hardness of their corresponding problems in terms of time.
1 Introduction
1.1 Background
Lately there has been a concentrated effort to understand the time complexity within P, the class of decision problems solvable by polynomial time algorithms. The main goal is to explain why certain problems have time complexity that seems to be non-optimal. For example, all known efficient algorithmic solutions for the 3SUM problem, where we seek to determine whether there are three elements in input set of size such that , take time111The and notations suppress polylogarithmic factors. However, the only real lower bound that we know is the trivial . Likewise, we know how to solve the all pairs shortest path, APSP, problem in time but we cannot even determine whether it is impossible to obtain an time algorithm. One may note that it follows from the time-hierarchy theorem that there exist problems in P with complexity for every fixed . Nevertheless, such a separation for natural practical problems seems to be hard to achieve.
The collaborated effort to understand the internals of P has been concentrated on identifying some basic problems that are conjectured to be hard to solve more efficiently (by polynomial factors) than their current known complexity. These problems serve as a basis to prove conditional hardness of other problems by using reductions. The reductions are reminiscent of NP-complete reductions but differ in that they are restricted to be of time complexity strictly smaller (by a polynomial factor) than the problem that we are reducing to. Examples of such hard problems include the well-known 3SUM problem, the fundamental APSP problem, (combinatorial) Boolean matrix multiplication, etc. Recently, conditional time lower bounds have been proven based on the conjectured hardness of these problems for graph algorithms [4, 42], edit distance [13], longest common subsequence (LCS) [3, 15], dynamic algorithms [5, 36], jumbled indexing [11], and many other problems [1, 2, 6, 7, 14, 25, 31, 34, 40].
1.2 Motivation
In stark contrast to polynomial time lower bounds, little effort has been devoted to finding polynomial space conditional lower bounds. An example of a space lower bound appears in the work of Cohen and Porat [19] and Pǎtraşcu and Roditty [38] where lower bounds are shown on the size of a distance oracle for sparse graphs based on a conjecture about the best possible data structure for a set intersection problem (which we call set disjointness in order to differ it from its reporting variant).
A more general question is, for algorithmic problems, what conditional lower bounds of a space/time tradeoff can be shown based on the set disjointness (intersection) conjecture? Even more general is to discover what space/time tradeoffs can be achieved based on the other algorithmic problems that we assumed are hard (in the time sense)? Also, what are the relations between these identified ”hard” problems in the space/time tradeoff sense? These are the questions which form the basis and framework of this paper.
Throughout this paper we show connections between different hardness assumptions, show some matching upper bounds and propose several conjectures based on this accumulated knowledge. Moreover, we conjecture that there is a strong correlation between polynomial hardness in time and space. We note that in order to discuss space it is often more natural to consider data structure variants of problems and this is the approach we follow in this paper.
1.3 Our Results
Set Disjointness.
In the SetDisjointness problem mentioned before, it is required to preprocess a collection of sets , where is the universe of elements and the total number of elements in all sets is . For a query, a pair of integers is given and we are asked whether is empty or not. A folklore conjecture, which appears in [18, 38], suggests that to achieve a constant query time the space of the data structure constructed in the preprocessing stage needs to be . We call this conjecture the SetDisjointness conjecture. This conjecture does not say anything about the case where we allow higher query time. Therefore, we suggest a stronger conjecture which admits a full tradeoff between the space consumed by the data structure (denoted by ) and the query time (denoted by ). This is what we call the Strong SetDisjointness conjecture. This conjecture states that for solving SetDisjointness with a query time our data structure needs space. A matching upper bound exists for this problem by generalizing ideas from [18] (see also [32]). Our new SetDisjointness conjecture can be used to admit more expressive space lower bounds for a full tradeoff between space and query time.
3SUM Indexing.
One of the basic and frequently used hardness conjectures is the celebrated 3SUM conjecture. This conjecture was used for about 20 years to show many conditional time lower bounds on various problems. However, we focus on what can be said about its space behavior. To do this, it is natural to consider a data structure version of 3SUM which allows one to preprocess the input set . Then, the query is an external number for which we need to answer whether there are such that . It was pointed out by Chan and Lewenstein [16] that all known algorithms for 3SUM actually work within this model as well. We call this problem 3SUM Indexing. On one hand, this problem can easily be solved using space by sorting for all and then searching for in time. On the other hand, by just sorting we can answer queries by a well-known linear time algorithm. The big question is whether we can obtain better than space while using just time query? Can it be done even if we allow query time? This leads us to our two new hardness conjectures. The 3SUM-Indexing conjecture states that when using query time we need space to solve 3SUM-Indexing. In the Strong 3SUM-Indexing conjecture we say that even when using query time we need space to solve 3SUM-Indexing.
3SUM Indexing and Set Disjointness.
We prove connections between the SetDisjointness conjectures and the 3SUM-Indexing conjectures. Specifically, we show that the Strong 3SUM-Indexing conjecture implies the Strong SetDisjointness conjecture, while the SetDisjointness conjecture implies the 3SUM-Indexing conjecture. This gives some evidence towards establishing the difficulty within the 3SUM-Indexing conjectures. The usefulness of these conjectures should not be underestimated. As many problems are known to be 3SUM-hard these new conjectures can play an important role in achieving space lower bounds on their corresponding data structure variants. Moreover, it is interesting to point on the difference between SetDisjointness which admits smooth tradeoff between space and query time and 3SUM-Indexing which admits a big gap between the two trivial extremes. This may explain why we are unable to show full equivalence between the hardness conjectures of the two problems. Moreover, it can suggest a separation between problems with smooth space-time behavior and others which have no such tradeoff but rather two ”far” extremes.
Generalizations.
Following the discussion on the SetDisjointness and the 3SUM-Indexing conjectures we investigate their generalizations.
I. k-Set Disjointness and (k+1)-SUM Indexing.
The first generalization is a natural parametrization of both problems. In the SetDisjointness problem we query about the emptiness of the intersection between two sets, while in the 3SUM-Indexing problem we ask, given a query number , whether two numbers of the input sum up to . In the parameterized versions of these problems we are interested in the emptiness of the intersection between k sets and ask if k numbers sum up to a number given as a query. These generalized variants are called k-SetDisjointness and (k+1)-SUM-Indexing respectively. For each problem we give corresponding space lower bounds conjectures which generalize those of SetDisjointness and 3SUM-Indexing. These conjectures also have corresponding strong variants which are accompanied by matching upper bounds. We prove that the k-SetDisjointness conjecture implies (k+1)-SUM-Indexing conjecture via a novel method using linear equations.
II. k-Reachability.
A second generalization is the problem we call k-Reachability. In this problem we are given as an input a directed sparse graph for preprocessing. Afterwards, for a query, given as a pair of vertices , we wish to return if there is a path from to consisting of at most edges. We provide an upper bound on this problem for every fixed . The upper bound admits a tradeoff between the space of the data structure (denoted by ) and the query time (denoted by ), which is . We argue that this upper bound is tight. That is, we conjecture that if query takes time, the space must be . We call this conjecture the k-Reachability conjecture.
We give three indications towards the correctness of this conjecture. First, we prove that the base case, where , is equivalent to the SetDisjointness problem. This is why this problem can be thought of as a generalization of SetDisjointness.
Second, if we consider non-constant then the smooth tradeoff surprisingly disappears and we get ”extreme behavior” as eventually becomes . This means that to answer reachability queries for non-constant path length, we can either store all answers in advance using space or simply answer queries from scratch using a standard graph traversal algorithm. The general problem where the length of the path from to is unlimited in length is sometimes referred to as the problem of constructing efficient reachability oracles. Pǎtraşcu in [37] leaves it as an open question if a data structure with less than space can answer reachability queries efficiently. Moreover, Pǎtraşcu proved that for constant time query, truly superlinear space is needed. Our k-Reachability conjecture points to this direction, while admitting full space-time tradeoff for constant .
The third indication for the correctness of the k-Reachability conjecture comes from a connection to distance oracles. A distance oracle is a data structure that can be used to quickly answer queries about the shortest path between two given nodes in a preprocessed undirected graph. As mentioned above, the SetDisjointness conjecture was used to exclude some possible tradeoffs for sparse graphs. Specifically, Cohen and Porat [19] showed that obtaining an approximation ratio smaller than 2 with constant query time requires space. Using a somewhat stronger conjecture Pǎtraşcu and Roditty [38] showed that a (2,1)-distance oracle for unweighted graphs with edges requires space. Later, this result was strengthened by Pǎtraşcu et al. [39]. However, these results do not exclude the possibility of compact distance oracles if we allow higher query time. For stretch-2 and stretch-3 in sparse graphs, Agarwal et. al. [9, 10] achieved a space-time tradeoff of and , respectively. Agarwal [8] also showed many other results for stretch-2 and below. We use our k-Reachability conjecture to prove that for stretch-less-than-(1+2/k) distance oracles is bounded by . This result is interesting in light of Agarwal [8] where a stretch-(5/3) oracle was presented which achieves a space-time tradeoff of . This matches our lower bound, where , if our lower bound would hold not only for stretch-less-than-(5/3) but also for stretch-(5/3) oracles. Consequently, we see that there is strong evidence for the correctness of the k-Reachability conjecture.
Moreover, these observations show that on one hand k-Reachability is a generalization of SetDisjointness which is closely related to 3SUM-Indexing. On the other hand, k-Reachability is related to distance oracles which solve the famous APSP problem using smaller space by sacrificing the accuracy of the distance between the vertices. Therefore, the k-Reachability conjecture seems as a conjecture corresponding to the APSP hardness conjecture, while also admitting some connection with the celebrated 3SUM hardness conjecture.
SETH and Orthogonal Vectors.
After considering space variants of the 3SUM and APSP conjectures it is natural to consider space variants for the Strong Exponential Time Hypothesis (SETH) and the closely related conjecture of orthogonal vectors. SETH asserts that for any there is an integer such that k-SAT cannot be solved in time. The orthogonal vectors time conjecture states that there is no algorithm that for every , finds if there are at least two orthogonal vectors in a set of Boolean vectors of length in time. We discuss the space variants of these conjectures in Section 7. However, we are unable to connect these conjectures and the previous ones. This is perhaps not surprising as the connection between SETH and the other conjectures even in the time perspective is very loose (see, for example, discussions in [5, 25]).
Boolean Matrix Multiplication.
Another problem which receives a lot of attention in the context of conditional time lower bounds is calculating Boolean Matrix Multiplication (BMM). We give a data structure variant of this well-known problem. We then demonstrate the connection between this problem and the problems of SetDisjointness and k-Reachability.
Applications.
Finally, armed with the space variants of many well-known conditional time lower bounds, we apply this conditional space lower bounds to some static and dynamic problems. This gives interesting space lower bound results on these important problems which sometimes also admits clear space-time tradeoff. We believe that this is just a glimpse of space lower bounds that can be achieved based on our new framework and that many other interesting results are expected to follow this promising route.
Figure 1 in Appendix 0.A presents a sketch of the results in this paper.
2 Set Intersection Hardness Conjectures
We first give formal definitions of the SetDisjointness problem and its enumeration variant:
Problem 1 (SetDisjointness Problem)
Preprocess a family of sets, all from universe , with total size so that given two query sets one can determine if .
Problem 2 (SetIntersection Problem)
Preprocess a family of sets, all from universe , with total size so that given two query sets one can enumerate the set .
Conjectures.
The SetDisjointness problem was regarded as a problem that admits space hardness. The hardness conjecture of the SetDisjointness problem has received several closely related formulations. One such formulation, given by Pǎtraşcu and Roditty [38], is as follows:
Conjecture 1
SetDisjointness Conjecture [Formulation 1]. Any data structure for the SetDisjointness problem where for a large enough constant and with a constant query time must use space.
Another formulation is implicitly suggested in Cohen and Porat [18]:
Conjecture 2
SetDisjointness Conjecture [Formulation 2]. Any data structure for the SetDisjointness problem with constant query time must use space.
There is an important distinction between the two formulations, which is related to the sparsity of SetDisjointness instances. This distinction follows from the following upper bound: store an matrix of the answers to all possible queries, and then queries will cost constant time. The first formulation of the SetDisjointness conjecture states that if we want constant (or poly-logaritmic) query time, then this is the best we can do. At a first glance this makes the second formulation, whose bounds are in terms of and not , look rather weak. In particular, why would we ever be interested in a data structure that uses space when we can use one with space? The answer is that the two conjectures are the same if the sets are very sparse, and so at least in terms of , if one were to require a constant query time then by the second formulation the space must be at least (which happens in the very sparse case).
Nevertheless, we present a more general conjecture, which in particular captures a tradeoff curve between the space usage and query time. This formulation captures the difficulty that is commonly believed to arise from the SetDisjointness problem, and matches the upper bounds of Cohen and Porat [18] (see also [32]).
Conjecture 3
Strong SetDisjointness Conjecture. Any data structure for the SetDisjointness problem that answers queries in time must use space.
For example, a natural question to ask is “what is the smallest query time possible with linear space?”. This question is addressed, at least from a lower bound perspective, by the Strong SetDisjointness conjecture.
Conjecture 4
Strong SetIntersection Conjecture. Any data structure for the SetIntersection problem that answers queries in time, where is the size of the output of the query, must use space.
3 3SUM-Indexing Hardness Conjectures
In the classic 3SUM problem we are given an integer array of size and we wish to decide whether there are 3 distinct integers in which sum up to zero. Gajentaan and Overmars [23] showed that an equivalent formulation of this problem receives 3 integer arrays , , and , each of size , and the goal is to decide if there is a triplet , and that sum up to zero.
We consider the data structure variant of this problem which is formally defined as follows:
Problem 3 (3SUM-Indexing Problem)
Preprocess two integer arrays and , each of length , so that given a query integer we can decide whether there are and such that .
It is straightforward to maintain all possible sums of pairs in quadratic space, and then answer a query in time. On the other extreme, if one does not wish to utilize more than linear space then one can sort the arrays separately during preprocssing time, and then a query can be answered in time by scanning both of the sorted arrays in parallel and in opposite directions.
We introduce two conjectures with regards to the 3SUM-Indexing problem, which serve as natural candidates for proving polynomial space lower bounds.
Conjecture 5
3SUM-Indexing Conjecture: There is no solution for the 3SUM-Indexing problem with truly subquadratic space and query time.
Conjecture 6
Strong 3SUM-Indexing Conjecture: There is no solution for the 3SUM-Indexing problem with truly subquadratic space and truly sublinear query time.
Notice that one can solve the classic 3SUM problem using a data structure for 3SUM-Indexing by preprocessing and , and answering 3SUM-Indexing queries on all of the values in .
Next, we prove theorems that show tight connections between the 3SUM-Indexing conjectures and the SetDisjointness conjectures. We note that the proofs of the first two theorems are similar to the proofs of [31], but with space interpretation.
Theorem 3.1
The Strong 3SUM-Indexing Conjecture implies the Strong SetDisjointness Conjecture.
Proof
A family of hash functions from is called linear if for any and any , , where is some integer that depends only on . is called almost linear if for any and any , either , or .
Given a hash function we say that a value is heavy for set if . is called almost balanced if for any set , the expected number of elements from that are hashed to heavy values is . Kopelowitz et al. showed in [31] that a family of hash functions obtained from the construction of Dietzfelbinger [20] is almost-linear, almost-balanced, and pair-wise independent. In order to reduce clutter in the proof here we assume the existence of linear, almost-balanced, and pair-wise independent families of hash functions. Using the family of hash functions of Dietzfelbinger [20] will only affect multiplicative constants.
We reduce an instance of the 3SUM-Indexing problem to an instance of the SetDisjointness problem as follows. Let for some constant . Let . Without loss of generality we assume that is an integer. We pick a random hash function from a family that is linear and almost-balanced. Using we create buckets such that , and another buckets such that . Since is almost-balanced, the expected number of elements from and that are mapped to buckets of size greater than is . We use space to maintain this list explicitly, together with a lookup table for the elements in and .
Next, we pick a random hash function where is chosen from a pair-wise independent and linear family. For each bucket we create shifted sets as follows: for each let and . These sets are all preprocessed into a data structure for the SetDisjointness problem.
Next, we answer a 3SUM-Indexing query by utilizing the linearity of and , which implies that if there exist and such that then and .
Thus, if then must be in . For each we would like to intersect with in order to find candidate pairs of and . Denote by and . Due to the almost-linearity of , if the sets and are not disjoint then the sets and are not disjoint (but the reverse is not necessarily true). Thus, if then there is no candidate pair in and . However, if then it is possible that this is due to a 3SUM-Indexing solution, but we may have false positives. Notice that the number of set pairs whose intersection we need to examine is since is given. Once we pick ( choices) the rest is implicit.
Set and let . Since is pair-wise independent and linear then for any pair where we have that if then . Since each bucket contains at most elements, the probability of a false positive due to two buckets and is not greater than . In order to reduce the probability of a false positive to be polynomially small, we repeat the process with different choices of functions (but using the same ). This blows up the number of sets by a factor of , but not the universe. If the sets intersect under all choices of then we can spend time to find and within buckets and , which are either a 3SUM-Indexing solution (and the algorithm halts), or a false positive, which only occurs with probability .
To summarize, we create a total of sets, each of size at most . Thus, the total size of the SetDisjointness instance is . For a query, we perform queries on the SetDisjointness structure, and spend another expected time to verify that we did not hit a false positive. Furthermore, we spend time to check possible solutions containing one of the expected elements from buckets with too many elements by using the lookup tables. If we denote by and the query time and space usage, respectively, of the SetDisjointness data structure on elements (in our case ), then the query time of the reduction becomes time and the space usage is . Since we may assume that , we have that .
By the Strong 3SUM-Indexing Conjecture, either or , which means that either or . For any constant , if the SetDisjointness data structure uses space, then . Since this holds for any it must be that . ∎
Theorem 3.2
The Strong 3SUM-Indexing Conjecture implies the Strong SetIntersection Conjecture.
Proof
The proof follows the same structure as the proof of Theorem 3.1, but here we set , where is a constant. Furthermore, we preprocess the buckets using a SetIntersection data structure, and if two sets intersect then instead of repeating the whole process with different choices of (in order to reduce the probability of a false positive), we use the SetIntersection data structure to report all of the elements in an intersection, and verify them all directly.
As before, set and let . Since is pair-wise independent and linear then for any pair where we have that if then . We now bound the expected output size from all of the intersections. Since each pair of buckets imply at most pairs of elements, the expected size of their intersection is . Thus, the expected size of the output of all of the intersections is . For each pair in an intersection we can verify in constant time if together with they form a solution.
To summarize, we create a total of sets, each of size at most . Thus, the total size of the SetIntersection instance is . For a query, we perform queries on the SetIntersection structure. Furthermore, we spend time to check possible solutions containing one of the expected elements from buckets with too many elements by using the lookup tables. If we denote by and the query time and space usage, respectively, of the SetIntersection data structure on elements (in our case ), then the query time of the reduction becomes time and the space usage is . Since we may assume that , we have that .
By the Strong 3SUM-Indexing conjecture, either or , which means that either or . For any constant , if the SetIntersection data structure uses space, then . Since this holds for any and any it must be that . ∎
Theorem 3.3
The SetDisjointness Conjecture implies the 3SUM-Indexing Conjecture.
Proof
Given an instance of SetDisjointness, we construct an instance of 3SUM-Indexing as follows. Denote with the value of the largest element in the SetDisjointness instance. Notice that we may assume that (otherwise we can use a straightforward renaming). For every element that is contained in at least one of the sets we create two integers and , which are represented by bits each (recall that is the number of sets).
The least significant bits in represent the value of . The following bit is a zero. The following bits in represent the index of the set containing , and the rest of the are all set to zero. The least significant bits in represent the value of . The following are all set to zero. The following bits in represent the index of the set containing , and the last bit is set to zero. Finally, the integer is added to of the 3SUM-Indexing instance, while the integer is added to .
We have created two sets of integers. We then preprocess them to answer 3SUM-Indexing queries. Now, to answer a SetDisjointness query on sets and , we query the 3SUM-Indexing data structure with an integer which is determined as follows. The least significant bits in represent the value of . The following bit is a zero. The following bits represent the index and are followed by a zero. The next bits represent the index and the last bit is set to zero.
It is straightforward to verify that there exists a solution to the 3SUM-Indexing problem on if and only if the sets and are not disjoint. Therefore, if there is a solution to the 3SUM-Indexing problem with less than space and constant query time then there is a solution for the SetDisjointness problem which refutes the SetDisjointness Conjecture. ∎
4 Parameterized Generalization:
k-Set Intersection and (k+1)-SUM
Two parameterized generalizations of the SetDisjointness and 3SUM-Indexing problems are formally defined as follows:
Problem 4 (k-SetDisjointness Problem)
Preprocess a family of sets, all from universe , with total size so that given query sets one can quickly determine if .
Problem 5 ((k+1)-SUM-Indexing Problem)
Preprocess integer arrays , each of length , so that given a query integer we can decide if there is such that .
It turn out that a natural generalization of the data structure of Cohen and Porat [18] leads to a data structure for k-SetDisjointness as shown in the following lemma.
Lemma 1
There exists a data structure for the k-SetDisjointness problem where the query time is and the space usage is .
Proof
We call the largest sets in large sets. The rest of the sets are called small sets. In the preprocessing stage we explicitly maintain a -dimensional table with the answers for all k-SetDisjointness queries where all sets are large sets. The space needed for such a table is . Moreover, for each set (large or small) we maintain a look-up table that supports disjointness queries (with this set) in constant time. Since there are large sets and the total number of elements is , the size of each of the small sets is at most .
Given a k-SetDisjointness query, if all of the query sets are large then we look up the answer in the -dimensional table. If at least one of the sets is small then using a brute-force search we look-up each of the at most elements in each of the other sets. Thus, the total query time is bounded by , and the space usage is . The rest follows. ∎
Notice that for the case of in Lemma 1 we obtain the same tradeoff of Cohen and Porat [18] for SetDisjointness. The following conjecture suggests that the upper bound of Lemma 1 is the best possible.
Conjecture 7
Strong k-SetDisjointness Conjecture. Any data structure for the k-SetDisjointness problem that answers queries in time must use space.
Similarly, a natural generalization of the Strong 3SUM-Indexing conjecture is the following.
Conjecture 8
Strong (k+1)-SUM-Indexing Conjecture. There is no solution for the (k+1)-SUM-Indexing problem with space and truly sublinear query time.
We also consider some weaker conjectures, similar to the SetDisjointness and 3SUM-Indexing conjectures.
Conjecture 9
k-SetDisjointness Conjecture. Any data structure for the k-SetDisjointness problem that answers queries in constant time must use space.
Conjecture 10
(k+1)-SUM-Indexing Conjecture. There is no solution for the (k+1)-SUM-Indexing problem with space and constant query time.
Similar to Theorem 3.3, we prove the following relationship between the k-SetDisjointness conjecture and the (k+1)-SUM-Indexing conjecture.
Theorem 4.1
The k-SetDisjointness conjecture implies the (k+1)-SUM-Indexing conjecture
Proof
Given an instance of k-SetDisjointness, we construct an instance of (k+1)-SUM-Indexing as follows. Denote by the value of the largest element in the SetDisjointness instance. Notice that we may assume that (otherwise we use a straightforward renaming). For every element that is contained in at least one of the sets we create integers , where each integer is represented by bits.
For integer , if the least significant bits are all set to zero, except for the bits in indices that represent the value of . If the value of the bits in the indices is set to for all . The following bits are all set to zero, except for the bits in indices which represent the index of the set containing .
We now create an instance of (k+1)-SUM-Indexing where the th input array is the set of integers for all that is contained in at least one set of our family. Thus, the size of each array is at most . Now, given a k-SetDisjointness query we must decide if . To answer this query we will query the instance of (k+1)-SUM-Indexing we have created with an integer whose binary representation is as follows: In the least significant bits the value of the bits in the indices is set to for all . In the following bits, the bits at locations represent (for ). The rest of the bits are padding zero bits (in between representations of various s and s).
If then by our construction it is straightforward to verify that the (k+1)-SUM-Indexing query on will return that there is a solution. If then at least for one the sum of values in the bits in indices in the least significant bits will not be . This is because we can view each block of bits in the least significant bits as solving a linear equation. This equation is of the form for every block where . The solution of each of these equations is for all . Consequently, a solution can be found only if there is a specific which is contained in all of the sets. Therefore, we get a correct answer to a k-SetDisjointness query by answering a (k+1)-SUM-Indexing query.
Consequently, if for some specific constant there is a solution to the (k+1)-SUM-Indexing problem with less than space and constant query time, then with this reduction we refute the k-SetDisjointness conjecture. ∎
5 Directed Reachability Oracles as a Generalization of Set Disjointness Conjecture
An open question which was stated by Pǎtraşcu in [37] asks if it is possible to preprocess a sparse directed graph in less than space so that Reachability queries (given two query vertices and decide whether there is a path from to or not) can be answered efficiently. A partial answer, given in [37], states that for constant query time truly superlinear space is necessary. In the undirected case the question is trivial and one can answer queries in constant time using linear space. This is also possible for planar directed graphs (see Holm et al. [27]).
We now show that Reachability oracles for sparse graphs can serve as a generalization of the SetDisjointness conjecture. We define the following parameterized version of Reachability. In the k-Reachability problem the goal is to preprocess a directed sparse graph so that given a pair of distinct vertices one can quickly answer whether there is a path from to consisting of at most edges. We prove that 2-Reachability and SetDisjointness are tightly connected.
Lemma 2
There is a linear time reduction from SetDisjointness to 2-Reachability and vice versa which preserves the size of the instance.
Proof
Given a graph as an instance for 2-Reachability, we construct a corresponding instance of SetDisjointness as follows. For each vertex we create the sets and . We have sets and elements in all of them ( and ). Now, a query is reduced to determining if the sets and are disjoint or not. Notice, that the construction is done in linear time and preserves the size of the instance. In the opposite direction, we are given sets having elements in total . We can create an instance of 2-Reachability in the following way. For each set we create a vertex . Moreover, for each element we create a vertex . Then, for each element in a set we create two directed edges and . These vertices and edges define a directed graph, which is preprocessed for 2-Reachability queries. It is straightforward to verify that the disjointness of and is equivalent to determining if there is a path of length at most edges from to . Moreover, the construction is done in linear time and preserves the size of the instance. ∎
Furthermore, we consider k-Reachability for . First we show an upper bound on the tradeoff between space and query time for solving k-Reachability.
Lemma 3
There exists a data structure for k-Reachability with space and query time such that .
Proof
Let be an integer parameter to be set later. Given a directed graph , we call vertex a heavy vertex if and a vertex a light vertex if . Notice that the number of heavy vertices is at most . For all heavy vertices in we maintain a matrix containing the answers to any k-Reachability query between two heavy vertices. This uses space.
Next, we recursively construct a data structure for (k-1)-Reachability. Given a query , if both vertices are heavy then the answer is obtained from the matrix. Otherwise, either or is light vertex. Without loss of generality, say is a light vertex. We consider each vertex () and query the (k-1)-Reachability data structure with the pair . Since is a light node, there are no more than queries. One of the queries returns a positive answer if and only if there exists a path of length at most from to .
Denote by the space used by our k-Reachability oracle on a graph with vertices and denote by the corresponding query time. In our construction we have and . For it is easy to construct a linear space data structure using hashing so that queries can be answered in constant time. Thus, and . ∎
Notice that for the case of the upper bounds from Lemma 3 exactly match the tradeoff of the Strong SetDisjointness Conjecture (). We expand this conjecture by considering the tightness of our upper bound for k-Reachability, which then leads to some interesting consequences with regard to distance oracles.
Conjecture 11
Directed k-Reachability Conjecture. Any data structure for the k-Reachability problem with query time must use space.
Notice that when is non-constant then by our upper bound space is necessary independent of the query time. This fits nicely with what is currently known about the general question of Reachability oracles: either we spend space and answer queries in constant time or we do no preprocessing and then answer queries in linear time. This leads to the following conjecture.
Conjecture 12
Directed Reachability Hypothesis. Any data structure for the Reachability problem must either use space, or linear query time.
The conjecture states that in the general case of Reachability there is no full tradeoff between space and query time. We believe the conjecture is true even if the path is limited to lengths of some non-constant number of edges.
6 Distance Oracles and Directed Reachability
There are known lower bounds for constant query time distance oracles based on the SetDisjointness hypothesis. Specifically, Cohen and Porat [18] showed that stretch-less-than-2 oracles need space for constant queries. Patrascu et al. [39] showed a conditional space lower bound of for constant-time stretch-2 oracles. Applying the Strong SetDisjointness conjecture to the same argument as in [18] we can prove that for stretch-less-than-2 oracles the tradeoff between (the space for the oracle) and (the query time) is by .
Recent effort was taken toward constructing compact distance oracles where we allow non-constant query time. For stretch-2 and stretch-3 Agarwal et al. [10] [9] achieves a space-time tradeoff of and , respectively, for sparse graphs. Agarwal [8] also showed many other results for stretch-2 and below. Specifically, Agarwal showed that for any integer a stretch-(1+1/k) oracle exhibits the following space-time tradeoff: . Agarwal also showed a stretch-(1+1/(k+0.5)) oracle that exhibits the following tradeoff: . Finally, Agarwal gave a stretch-(5/3) oracle that achieves a space-time tradeoff of . Unfortunately, no lower bounds are known for non-constant query time.
Conditioned on the directed k-Reachability conjecture we prove the following lower bound.
Lemma 4
Assume the directed k-Reachability conjecture holds. Then stretch-less-than- distance oracles with query time must use space.
Proof
Given a graph for which we want to preprocess for k-Reachability, we create a layered graph with layers where each layer consists of a copy of all vertices of . Each pair of neighboring layers is connected by a copy of all edges in . We omit all directions from the edges. For every fixed integer , the layered graph has vertices and edges. Next, notice that if we construct a distance oracle that can distinguish between pairs of vertices of distance at most and pairs of vertices of distance at least , then we can answer k-Reachability queries. Consequently, assuming the k-Reachability conjecture we have that for stretch-less-than- distance oracles (For this is exactly the result we get by the SetDisjointness hypothesis). ∎
Notice, that the stretch-(5/3) oracle shown by Agarwal [8] achieves a space-time tradeoff of . Our lower bound is very close to this upper bound since it applies for any distance oracle with stretch-less-than-, by setting .
7 SETH and Orthogonal Vectors Space Conjectures
Solving SAT using time where is number of variables in the formula can be easily done using only space. However, the question is how can we use space in the case that we have only a partial assignment of variables and we would like to quickly figure out whether this partial assignment can be completed to a full satisfying assignment or not. On one end, by using just space we can answer queries in time. On the other end, we can save the answers to all possible queries using space. It is not clear if there is some sort of a tradeoff in between these two. A related problem is the problem of Orthogonal Vectors (OV). In this problem one is given a collection of vectors of length and need to answer if there are two of them which are orthogonal to one another. A reduction from SETH to OV was shown in [41]. By this reduction given a k-CNF formula of variables one can transform it using time to instances of OV in which the vectors are of length (for any , where is the number of clauses of each sparse formula represented by one instance of OV). This reduction leads to the following conjecture regarding OV, which is based on SETH: There is no algorithm that, for every , solves the OV problem on boolean vectors of length in time.
We can consider a data structure variant of the OV problem, which we call OV indexing. Given a list of boolean vectors of length we should preprocess them and create a suitable data structure. Then, we answer queries of the following form: Given a vector , is there a vector in the list which is orthogonal to ?
We state the following conjecture which is the space variant of the well-studied OV (time) conjecture:
Conjecture 13
Orthogonal Vectors Indexing Hypothesis: There is no algorithm for every that solves the OV indexing problem with space and truly sublinear query time.
We note that we believe that the last conjecture is true even if we allow superpolynomial preprocessing time. Moreover, it seems that it also may be true even for some constant slightly larger than 2.
8 Space Requirements for Boolean Matrix Multiplication
Boolean Matrix Multiplication(BMM) is one of the most fundamental problems in Theoretical Computer Science. The question of whether computing the Boolean product of two Boolean matrices of size is possible in time is one of the most intriguing open problems. Moreover, finding a combinatorial algorithm for BMM taking time for some is considered to be impossible to do with current algorithmic techniques.
We focus on the following data structure version of BMM, preprocess two Boolean matrices and , such that given a query we can quickly return the value of where is the Boolean produce and . Since storing all possible answers to queries will require space in the worst case, we focus on the more interesting scenario where we have only space to store the outcome of the preprocessing stage. In case the input matrices are dense (the number of ones and the number of zeroes are both ) it seems that this can be hard to achieve as storing the input matrices alone will take space. So we consider a complexity model, which we call the read-only input model, in which storing the input is for free (say on read-only memory), and the space usage of the data structure is only related to the additional space used. We now demonstrate that BMM in the read-only input model is equivalent to SetDisjointness.
Lemma 5
BMM in the read-only input model and SetDisjointness are equivalent.
Proof
Given an instance of SetDisjointness let denote the elements in an input instance. We construct an instance of BMM as follows. Assume without loss of generality that all sets are not empty, and so . Row in matrix represents a set while each column represents element . An entry equals if and equals zero otherwise. We also set . We also pad each of the matrices with zeroes so their size will be . Clearly, in matrix , which is the product of and , is an indicator whether .
In the opposite direction, given two matrices and having ones we view each row of as a characteristic vector of a set (the elements in the set correspond to the ones in that row) and each column of as a characteristic vector of a set (the elements in the set corresponds to the ones in that column). Thus, the instance of SetDisjointness that have been created consists of set with elements. The value of an element in the product of and can be determined by the intersection of and . ∎
Another interesting connection between BMM and the other problems discussed in this paper is the connection to the problem of calculating the transitive closure of a graph, which is the general directed reachability mentioned above. It is well-known that BMM and transitive closure are equivalent in terms of time as shown by Fischer and Meyer [22]. But what happens if we consider space? It is easy to see that BMM can be reduced to transitive-closure (directed reachability) even in terms of space. However, the opposite direction is not clear as the reduction for time involves recursive squaring, which cannot be implemented efficiently in terms of space.
Another fascinating variant of BMM is the one in which an matrix is input for preprocessing and afterwards we need to calculate the result of multiplying it by a given query vector . This can be seen as the space variant of the celebrated OMV (online matrix-vector) problem discussed by Henzinger et al. [25]. It is interesting to see if one can make use of a data structure so that consecutive vector queries can be answered in time.
9 Applications
We now provide applications of our rich framework for proving conditional space lower bounds. In the following subsections we consider both static and dynamic problems.
9.1 Static Problems
9.1.1 Edge Triangles
The first example we consider is in regards to triangles. In a problem that is called edge triangles detection, we are given a graph to preprocess and then we are given an edge as a query and need to answer whether belongs to a triangle. In a reporting variant of this problem, called edge triangles we need not only to answer if belongs to a triangle but also report all triangles it belongs to. This problem was considered in [12].
It can be easily shown that these problems are equivalent to SetDisjointness and SetIntersection. We just construct a set per each vertex containing all its neighbors. Querying if there is a triangle containing the edge is equivalent to asking if is empty or not. Considering the reporting variant, reporting all triangles containing is thus equivalent to finding all the elements in . Therefore, we get the following results:
Theorem 9.1
Assume the Strong SetDisjointness conjecture. Suppose there is a data structure for edge triangles detection problem for a graph , with space and query time . Then .
Theorem 9.2
Assume the Strong SetIntersection conjecture. Suppose there is a data structure for edge triangles problem for a graph , with space and query time time, where is the size of the output of the query. Then .
9.1.2 Histogram Indexing
A histogram, also called a Parikh vector, of a string over alphabet is a -length vector containing the character count of . For example, for the histogram is . In the histogram indexing problem we preprocess an -length string to support the following queries: given a query histogram , return whether there is a substring of such that .
This problem has received much attention in the recent years. The case where the alphabet size is 2 (binary alphabet) was especially studied. A simple algorithm for this case solves the problem in preprocessing time and constant query time. There was a concentrated effort to reduce the quadratic preprocessing time for some years. However, an algorithm with preprocessing time that is for some was unknown until a recent breakthrough by Chan and Lewenstein [16]. They showed an algorithm with preprocessing time and constant query time. For alphabet size they obtained an algorithm with preprocessing time and query time for . Regarding space complexity, it is well known how to solve histogram indexing for binary alphabet using linear space and constant query time. For alphabet size , Kociumaka et al. [30] presented a data structure with space and query time. Chan and Lewenstein [16] improved their result and showed a solution by a data structure using space with only query time.
Amir et al. [11] proved conditional lower bound on the tradeoff between the preprocessing and query time of the histogram indexing problem. Very recently, their lower bound was improved and generalized by Goldstein et al. [24]. Following the reduction by Goldstein et al. [24] and utilizing our framework for conditional space lower bounds, we obtain the following lower bound on the tradeoff between the space and query time of histogram indexing:
Theorem 9.3
Assume the Strong 3SUM-Indexing conjecture holds. The histogram indexing problem for a string of length and constant alphabet size cannot be solved with space and query time, for any .
Proof
We use the same reduction as in [24]. This time it will be used to reduce an instance of 3SUM-Indexing (on numbers) to histogram indexing, instead of reducing from an instance of 3SUM. The space consumed by the reduction is dominated by the space needed to prepare a histogram indexing instance with string length for histogram queries. The number of histogram queries we do for each query number of the 3SUM-Indexing instance is . The query time is dominated by the time required by these queries. Let denote the space required by a data structure for histogram indexing on -length string over alphabet size and let denote the query time for the same parameters. Assuming the strong 3SUM-Indexing conjecture and following our reduction, we have that and . Plugging in the value of in terms of we get the required lower bound. ∎
If we plug in the previous theorem , we get that if the strong 3SUM-Indexing conjecture is true we cannot have a solution for histogram indexing with space and query time. This lower bound is very close to the upper bound obtained by Chan and Lewenstein [16] as there is only a gap of in the power of in the query time. Moreover, if the value of becomes close to 0 (so the value of is close to 1) the upper bound and the lower bound get even closer to each other. This is very interesting, as it means that to get truly subquadratic space solution for histogram indexing for alphabet size greater than 2, we will have to spend polynomial query time. This is in stark contrast to the simple linear space solution for histogram indexing over binary alphabets that supports queries in constant time.
Following reductions presented in [31], from SetIntersection or SetDisjointness to several other problems, we are able to show that based on the Strong SetDisjointness conjecture, the same problems admit a space/query time lower bounds. For sake of completeness, we reproduce these reductions in the next three subsections and show that they admit the space lower bounds as needed.
9.1.3 Distance Oracles for Colors
Let be a set of points in some metric with distance function , where each point has some associated colors . For we denote by the set of points from with color . We generalize so that the distance between a point and a color is denoted by . In the (Approximate) Distance Oracles for Vertex-Labeled Graphs problem [17, 26] we are interested in preprocessing so that given a query of a point and a color we can return (or some approximation). We further generalize so that the distance between two colors and is denoted by . In the Distance Oracle for Colors problem we are interested in preprocessing so that given two query colors and we can return . In the Approximate Distance Oracle for Colors problem we are interested in preprocessing and some constant so that given two query colors and we can return some value such that .
We show evidence of the hardness of the Distance Oracle for Colors problem and the Approximate Distance Oracle for Colors problem by focusing on the 1-D case.
Theorem 9.4
Assume the Strong SetDisjointness conjecture. Suppose there is a 1-D Distance Oracle for Colors with constant stretch for an input array of size with space and query time . Then .
Proof
We reduce SetDisjointness to the Colored Distance problem as follows. For each set we define a unique color . For an element ( is the universe of the elements in our sets) let denote the number of sets containing and notice that . Since each element in appears in at most sets, we partition into parts where the part contains all of the elements such that . An array is constructed from by assigning an interval in to each such that no two intervals overlap. Every interval contains all the colors of sets that contain . This implies that . Furthermore, for each and we separate from with a dummy color listed times at locations .
We can now simulate a SetDisjointness query on subsets by performing a colored distance query on colors and in each of the arrays. There exists a for which the two points returned from the query are at distance strictly less than if and only if there is an element in that is contained in both and . The space usage is and the query time is . The rest follows directly from the Strong SetDisjointness conjecture.
Finally, notice that the lower bound also holds for the approximate case, as for any constant the reduction can overcome the approximation by separating intervals using listings of . ∎
9.1.4 Document Retrieval Problems with Multiple Patterns
In the Document Retrieval problem [35] we are interested in preprocessing a collection of documents where , so that given a pattern we can quickly report all of the documents that contain . Typically, we are interested in run time that depends on the number of documents that contain and not in the total number of occurrences of in the entire collection of documents. In the Two Patterns Document Retrieval problem we are given two patterns and during query time, and wish to report all of the documents that contain both and . We consider two versions of the Two Patterns Document Retrieval problem. In the decision version we are only interested in detecting if there exists a document that contains both patterns. In the reporting version we are interested in enumerating all documents that contain both patterns.
All known solutions for the Two Patterns Document Retrieval problem with non trivial preprocessing use at least time per query [18, 28, 29, 35]. In a recent paper, Larsen, Munro, Nielsen, and Thankachan [33] show lower bounds for the Two Patterns Document Retrieval problem conditioned on the hardness of boolean matrix multiplication.
It is straightforward to see that the appropriate versions of the two pattern document retrieval problem solve the corresponding versions of the SetDisjointness and SetIntersection problems. In particular, this can be obtained by creating an alphabet (one character for each set), and for each we create a document that contains the characters corresponding to the sets that contain . The intersection between and directly corresponds to all the documents that contain both and . Thus, all of the lower bound tradeoffs for intersection problems are lower bound tradeoffs for the two pattern document retrieval problem.
Theorem 9.5
Assume the Strong SetDisjointness conjecture. Suppose there is a data structure for the decision version of the Two Patterns Document Retrieval problem for a collection of documents where , with space and query time . Then .
Theorem 9.6
Assume the Strong SetIntersection conjecture. Suppose there is a data structure for the reporting version of the Two Patterns Document Retrieval problem for a collection of documents where , with space and query time where is the size of the output. Then .
9.1.5 Forbidden Pattern Document Retrieval
In the Forbidden Pattern Document Retrieval problem [21] we are also interested in preprocessing the collection of documents but this time given a query and we are interested in reporting all of the documents that contain and do not contain . Here too we consider a decision version and a reporting version.
All known solutions for the Forbidden Pattern Document Retrieval problem with non trivial preprocessing use at least time per query [21, 29]. In a recent paper, Larsen, Munro, Nielsen, and Thankachan [33] show lower bounds for the Forbidden Pattern Document Retrieval problem conditioned on the hardness of boolean matrix multiplication.
Theorem 9.7
Assume the Strong 3SUM-Indexing conjecture. Suppose there is a data structure for the decision version of the Forbidden Pattern Document Retrieval problem for a collection of documents where , with space and query time . Then .
Proof
We will make use of the hard instance of SetDisjointness that was used in order to prove Theorem 3.1, and reduce this specific hard instance to the decision version of the Forbidden Pattern Document Retrieval problem. Recall that the size of this hard instance is , the universe size is , the number of sets is , and we need to perform SetDisjointness queries in order to answer one 3SUM-Indexing query.
Similar to the proof of Theorem 9.5 we set (one character for each set). However, this time for each we create a document that contains all the characters corresponding to sets that contain and all the characters corresponding to sets that do not contain .
The reason that we prove our lower bound based on the Strong 3SUM-Indexing conjecture and not on the Strong SetDisjointness conjecture is because the size of our instance can become rather large relative to (as the number of sets that do not contain an element can be extremely large).
Thus, the size of the Forbidden Pattern Document Retrieval instance is , and the number of queries to answer is . Notice that the size of the instance enforces to be strictly larger than . By the Strong 3SUM-Indexing conjecture, either or , and so . For any constant , if the Forbidden Pattern Document Retrieval data structure uses space, then . Since this holds for any it must be that . ∎
Notice that if we only allow linear space then we obtain a query time lower bound of .
Theorem 9.8
Assume the Strong 3SUM-Indexing conjecture. Suppose there is a data structure for the reporting version of the Forbidden Pattern Document Retrieval problem for a collection of documents where , with space and query time where is the size of the output. Then .
Proof
Our proof is similar to the proof of Theorem 9.7, only this time we use the hard instance of SetIntersection from Theorem 3.2. So the number of queries is , the size of the universe is , the number of sets is , and the total size of the output is .
Thus, the size of the Forbidden Pattern Document Retrieval instance is , and the number of queries to answer is . Notice that the size of the instance enforces . By the Strong 3SUM-Indexing conjecture, either or , and so . For any constant , if the Forbidden Pattern Document Retrieval data structure uses space, then . Since this holds for any and since we can make as small as we like, it must be that . ∎
9.2 Dynamic Problems
We show space lower bounds on dynamic problems. Lower bounds for these problems from the time perspective were considered by Abboud and Vassilevska-Williams [5]. The first dynamic problem we consider is st-SubConn which is defined as follows. Given an undirected graph , two fixed vertices and and a set , answer whether and are connected using vertices form only. Vertices can be added or removed from .
The SetDisjointness problem can be reduced to st-SubConn. Given an instance of SetDisjointness we create an undirected graph as follows. We first create two unique vertices and . Then, for each set we create two vertices and and for each element we create a vertex . Moreover, we define . Initially the set contains and and all the s. Given a query asking about the emptiness of , we add and to the set . Then, we ask if and are connected, if so we know that is not empty as the only way to get from to is following and and some node representing a common element of and . If and are not connected then it is clear that the intersection is empty. After the query we remove the two vertices we have added so other queries can be handled properly. By this construction we get the following result:
Theorem 9.9
Assume the Strong SetDisjointness conjecture. Suppose there is a data structure for st-SubConn problem for a graph , with space and update and query time . Then .
There are other dynamic problems that st-SubConn can be efficiently reduced to, as shown by Abboud and Vssilevska-Williams [5]. This includes the following 3 problems:
Problem 6
(s,t)-Reachability (st-Reach). Maintain a directed graph subject to edge insertions and deletions, so that queries about the reachability of fixed vertices and can be answered quickly.
Problem 7
Bipartite Perfect Matching (BPMatch). Preprocess and maintain undirected bipartite graph subject to edge insertions and deletions, so that we can quickly answer if the graph has perfect matching.
Problem 8
Strong Connectivity (SC). Preprocess and maintain directed graph subject to edge insertions and deletions, so that we can quickly answer if the graph is strongly connected
Using our last theorem and the reductions by Abboud and Vassilevska-Williams [5], noting that they do not effect the space usage, we get the following:
Theorem 9.10
Assume the Strong SetDisjointness conjecture. Suppose there is a data structure for st-Reach/ BPMatch/ SC problem for a graph , with space and update and query time . Then .
We can get better lower bound for these 3 problems on sparse graphs based on the directed reachability conjecture. Given a sparse graph as an instance of directed reachability we can reduce it to an instance of st-Reach by just adding to special nodes and to the graph. Then, we can answer queries of the form ”Is reachable from ?” by inserting two edges and and asking if is reachable from . After the query we can restore the initial state by deleting these two edges. Thus, by using the reductions from st-Reach to BPMatch and SC as shown in [5], we get the following hardness result:
Theorem 9.11
Assume the Directed Reachability conjecture. Any data structure for the st-Reach/ BPMatch/ SC problem on sparse graphs can not have update and query time and space.
Appendix
Appendix 0.A Sketch of the Main Results
The reference list from the paper itself. Each links out to its DOI / PubMed record.
- 1[1] Amir Abboud, Arturs Backurs, Thomas Deuholm Hansen, Virginia Vassilevska Williams, and Or Zamir. Subtree isomorphism revisited. In Proc. of 27th ACM-SIAM Symposium on Discrete Algorithms, SODA , pages 1256–1271, 2016.
- 2[2] Amir Abboud, Arturs Backurs, and Virginia Vassilevska Williams. If the current clique algorithms are optimal, so is Valiant’s parser. 55th IEEE Annual Symposium on Foundations of Computer Science, FOCS , pages 98–117, 2015.
- 3[3] Amir Abboud, Arturs Backurs, and Virginia Vassilevska Williams. Quadratic-time hardness of LCS and other sequence similarity measures. 55th IEEE Annual Symposium on Foundations of Computer Science, FOCS , pages 59–78, 2015.
- 4[4] Amir Abboud, Fabrizio Grandoni, and Virginia Vassilevska Williams. Subcubic equivalences between graph centrality problems, APSP and diameter. In Proceedings of the Twenty-Sixth Annual ACM-SIAM Symposium on Discrete Algorithms, SODA 2015, San Diego, CA, USA, January 4-6, 2015 , pages 1681–1697, 2015.
- 5[5] Amir Abboud and Virginia Vassilevska Williams. Popular conjectures imply strong lower bounds for dynamic problems. In 55th IEEE Annual Symposium on Foundations of Computer Science, FOCS 2014, Philadelphia, PA, USA, October 18-21, 2014 , pages 434–443, 2014.
- 6[6] Amir Abboud, Virginia Vassilevska Williams, and Oren Weimann. Consequences of faster alignment of sequences. In Automata, Languages, and Programming - 41st International Colloquium, ICALP 2014, Copenhagen, Denmark, July 8-11, 2014, Proceedings, Part I , pages 39–51, 2014.
- 7[7] Amir Abboud, Virginia Vassilevska Williams, and Huacheng Yu. Matching triangles and basing hardness on an extremely popular conjecture. In Proceedings of the Forty-Seventh Annual ACM on Symposium on Theory of Computing, STOC 2015, Portland, OR, USA, June 14-17, 2015 , pages 41–50, 2015.
- 8[8] Rachit Agarwal. The space-stretch-time tradeoff in distance oracles. In Algorithms - ESA 2014 - 22th Annual European Symposium on Algorithms, Wroclaw, Poland, September 8-10, 2014. Proceedings , pages 49–60, 2014.
