The **knapsack problem** is the following problem in combinatorial optimization:

*Given a set of items, each with a weight and a value, determine which items to include in the collection so that the total weight is less than or equal to a given limit and the total value is as large as possible.*

It derives its name from the problem faced by someone who is constrained by a fixed-size knapsack and must fill it with the most valuable items. The problem often arises in resource allocation where the decision-makers have to choose from a set of non-divisible projects or tasks under a fixed budget or time constraint, respectively.

The knapsack problem has been studied for more than a century, with early works dating as far back as 1897.^{[1]}

Knapsack problems appear in real-world decision-making processes in a wide variety of fields, such as finding the least wasteful way to cut raw materials,^{[2]} selection of investments and portfolios,^{[3]} selection of assets for asset-backed securitization,^{[4]} and generating keys for the Merkle–Hellman^{[5]} and other knapsack cryptosystems.

One early application of knapsack algorithms was in the construction and scoring of tests in which the test-takers have a choice as to which questions they answer. For small examples, it is a fairly simple process to provide the test-takers with such a choice. For example, if an exam contains 12 questions each worth 10 points, the test-taker need only answer 10 questions to achieve a maximum possible score of 100 points. However, on tests with a heterogeneous distribution of point values, it is more difficult to provide choices. Feuerman and Weiss proposed a system in which students are given a heterogeneous test with a total of 125 possible points. The students are asked to answer all of the questions to the best of their abilities. Of the possible subsets of problems whose total point values add up to 100, a knapsack algorithm would determine which subset gives each student the highest possible score.^{[6]}

A 1999 study of the Stony Brook University Algorithm Repository showed that, out of 75 algorithmic problems related to the field of combinatorial algorithms and algorithm engineering, the knapsack problem was the 19th most popular and the third most needed after suffix trees and the bin packing problem.^{[7]}

The most common problem being solved is the **0-1 knapsack problem**, which restricts the number * of copies of each kind of item to zero or one. Given a set of ** items numbered from 1 up to **, each with a weight ** and a value **, along with a maximum weight capacity **,
*

- maximize
- subject to and .

Here * represents the number of instances of item ** to include in the knapsack. Informally, the problem is to maximize the sum of the values of the items in the knapsack so that the sum of the weights is less than or equal to the knapsack's capacity.
*

The **bounded knapsack problem** (**BKP**) removes the restriction that there is only one of each item, but restricts the number of copies of each kind of item to a maximum non-negative integer value :

- maximize
- subject to and

The **unbounded knapsack problem** (**UKP**) places no upper bound on the number of copies of each kind of item and can be formulated as above except that the only restriction on is that it is a non-negative integer.

- maximize
- subject to and

One example of the unbounded knapsack problem is given using the figure shown at the beginning of this article and the text "if any number of each book is available" in the caption of that figure.

The knapsack problem is interesting from the perspective of computer science for many reasons:

- The decision problem form of the knapsack problem (
*Can a value of at least*V*be achieved without exceeding the weight*W*?*) is NP-complete, thus there is no known algorithm that is both correct and fast (polynomial-time) in all cases. - There is no known polynomial algorithm which can tell, given a solution, whether it is optimal (which would mean that there is no solution with a larger
*V*). This problem is co-NP-complete. - There is a pseudo-polynomial time algorithm using dynamic programming.
- There is a fully polynomial-time approximation scheme, which uses the pseudo-polynomial time algorithm as a subroutine, described below.
- Many cases that arise in practice, and "random instances" from some distributions, can nonetheless be solved exactly.

There is a link between the "decision" and "optimization" problems in that if there exists a polynomial algorithm that solves the "decision" problem, then one can find the maximum value for the optimization problem in polynomial time by applying this algorithm iteratively while increasing the value of k. On the other hand, if an algorithm finds the optimal value of the optimization problem in polynomial time, then the decision problem can be solved in polynomial time by comparing the value of the solution output by this algorithm with the value of k. Thus, both versions of the problem are of similar difficulty.

One theme in research literature is to identify what the "hard" instances of the knapsack problem look like,^{[8]}^{[9]}^{[10]} or viewed another way, to identify what properties of instances in practice might make them more amenable than their worst-case NP-complete behaviour suggests.^{[11]}^{[12]} The goal in finding these "hard" instances is for their use in public-key cryptography systems, such as the Merkle–Hellman knapsack cryptosystem. More generally, better understanding of the structure of the space of instances of an optimization problem helps to advance the study of the particular problem and can improve algorithm selection.

Furthermore, notable is the fact that the hardness of the knapsack problem depends on the form of the input. If the weights and profits are given as integers, it is weakly NP-complete, while it is strongly NP-complete if the weights and profits are given as rational numbers.^{[13]} However, in the case of rational weights and profits it still admits a fully polynomial-time approximation scheme.

The NP-hardness of the Knapsack problem relates to computational models in which the size of integers matters (such as the Turing machine). In contrast, decision trees count each decision as a single step. Dobkin and Lipton^{[14]} show an lower bound on linear decision trees for the knapsack problem, that is, trees where decision nodes test the sign of affine functions.^{[15]} This was generalized to algebraic decision trees by Steele and Yao.^{[16]}
If the elements in the problem are real numbers or rationals, the decision-tree lower bound extends to the real random-access machine model with an instruction set that includes addition, subtraction and multiplication of real numbers, as well as comparison and either division or remaindering ("floor").^{[17]} This model covers more algorithms than the algebraic decision-tree model, as it encompasses algorithms that use indexing into tables. However, in this model all program steps are counted, not just decisions.
An *upper bound* for a decision-tree model was given by Meyer auf der Heide^{[18]} who showed that for every *n* there exists an *O*(*n*^{4})-deep linear decision tree that solves the subset-sum problem with *n* items. Note that this does not imply any upper bound for an algorithm that should solve the problem for *any given n*.

Several algorithms are available to solve knapsack problems, based on the dynamic programming approach,^{[19]} the branch and bound approach^{[20]} or hybridizations of both approaches.^{[11]}^{[21]}^{[22]}^{[23]}

The **unbounded knapsack problem** (**UKP**) places no restriction on the number of copies of each kind of item. Besides, here we assume that

- subject to and

Observe that has the following properties:

1. (the sum of zero items, i.e., the summation of the empty set).

2. , , where is the value of the -th kind of item.

The second property needs to be explained in detail. During the process of the running of this method, how do we get the weight ? There are only ways and the previous weights are where there are total kinds of different item (by saying different, we mean that the weight and the value are not completely the same). If we know each value of these items and the related maximum value previously, we just compare them to each other and get the maximum value ultimately and we are done.

Here the maximum of the empty set is taken to be zero. Tabulating the results from up through gives the solution. Since the calculation of each involves examining at most items, and there are at most values of to calculate, the running time of the dynamic programming solution is . Dividing by their greatest common divisor is a way to improve the running time.

Even if P≠NP, the complexity does not contradict the fact that the knapsack problem is NP-complete, since , unlike , is not polynomial in the length of the input to the problem. The length of the input to the problem is proportional to the number of bits in , , not to itself. However, since this runtime is pseudopolynomial, this makes the (decision version of the) knapsack problem a weakly NP-complete problem.

A similar dynamic programming solution for the 0-1 knapsack problem also runs in pseudo-polynomial time. Assume are strictly positive integers. Define to be the maximum value that can be attained with weight less than or equal to using items up to (first items).

We can define recursively as follows: **(Definition A)**

- if (the new item is more than the current weight limit)
- if .

The solution can then be found by calculating . To do this efficiently, we can use a table to store previous computations.

The following is pseudocode for the dynamic program:

```
// Input:
// Values (stored in array v)
// Weights (stored in array w)
// Number of distinct items (n)
// Knapsack capacity (W)
// NOTE: The array "v" and array "w" are assumed to store all relevant values starting at index 1.
array m[0..n, 0..W];
for j from 0 to W do:
m[0, j] := 0
for i from 1 to n do:
m[i, 0] := 0
for i from 1 to n do:
for j from 1 to W do:
if w[i] > j then:
m[i, j] := m[i-1, j]
else:
m[i, j] := max(m[i-1, j], m[i-1, j-w[i]] + v[i])
```

This solution will therefore run in time and space. (If we only need the value m[n,W], we can modify the code so that the amount of memory required is O(W) which stores the recent two lines of the array "m".)

However, if we take it a step or two further, we should know that the method will run in the time between and . From **Definition A**, we know that there is no need to compute all the weights when the number of items and the items themselves that we chose are fixed. That is to say, the program above computes more than necessary because the weight changes from 0 to W often. From this perspective, we can program this method so that it runs recursively.

```
// Input:
// Values (stored in array v)
// Weights (stored in array w)
// Number of distinct items (n)
// Knapsack capacity (W)
// NOTE: The array "v" and array "w" are assumed to store all relevant values starting at index 1.
Define value[n, W]
Initialize all value[i, j] = -1
Define m:=(i,j) // Define function m so that it represents the maximum value we can get under the condition: use first i items, total weight limit is j
{
if i == 0 or j <= 0 then:
value[i, j] = 0
return
if (value[i-1, j] == -1) then: // m[i-1, j] has not been calculated, we have to call function m
m(i-1, j)
if w[i] > j then: // item cannot fit in the bag
value[i, j] = value[i-1, j]
else:
if (value[i-1, j-w[i]] == -1) then: // m[i-1,j-w[i]] has not been calculated, we have to call function m
m(i-1, j-w[i])
value[i, j] = max(value[i-1,j], value[i-1, j-w[i]] + v[i])
}
Run m(n, W)
```

For example, there are 10 different items and the weight limit is 67. So, If you use above method to compute for , you will get this, excluding calls that produce :

Besides, we can break the recursion and convert it into a tree. Then we can cut some leaves and use parallel computing to expedite the running of this method.

To find the actual subset of items, rather than just their total value, we can run this after running the function above:

```
/**
* Returns the indices of the items of the optimal knapsack.
* i: We can include items 1 through i in the knapsack
* j: maximum weight of the knapsack
*/
function knapsack(i: int, j: int): Set<int> {
if i == 0 then:
return {}
if m[i, j] > m[i-1, j] then:
return {i} ∪ knapsack(i-1, j-w[i])
else:
return knapsack(i-1, j)
}
knapsack(n, W)
```

Another algorithm for 0-1 knapsack, discovered in 1974^{[24]} and sometimes called "meet-in-the-middle" due to parallels to a similarly named algorithm in cryptography, is exponential in the number of different items but may be preferable to the DP algorithm when is large compared to *n*. In particular, if the are nonnegative but not integers, we could still use the dynamic programming algorithm by scaling and rounding (i.e. using fixed-point arithmetic), but if the problem requires fractional digits of precision to arrive at the correct answer, will need to be scaled by , and the DP algorithm will require space and time.

algorithmMeet-in-the-middleisinput:A set of items with weights and values.output:The greatest combined value of a subset. partition the set {1...n} into two setsAandBof approximately equal size compute the weights and values of all subsets of each setfor eachsubsetofAdofind the subset ofBof greatest value such that the combined weight is less thanWkeep track of the greatest combined value seen so far

The algorithm takes space, and efficient implementations of step 3 (for instance, sorting the subsets of B by weight, discarding subsets of B which weigh more than other subsets of B of greater or equal value, and using binary search to find the best match) result in a runtime of . As with the meet in the middle attack in cryptography, this improves on the runtime of a naive brute force approach (examining all subsets of ), at the cost of using exponential rather than constant space (see also baby-step giant-step). The current state of the art improvement to the meet-in-the-middle algorithm, using insights from Schroeppel and Shamir's Algorithm for Subset Sum, provides as a corollary a randomized algorithm for Knapsack which preserves the (up to polynomial factors) running time and reduces the space requirements to (see ^{[25]} Corollary 1.4). In contrast, the best known deterministic algorithm runs in time with a slightly worse space complexity of .^{[26]}

As for most NP-complete problems, it may be enough to find workable solutions even if they are not optimal. Preferably, however, the approximation comes with a guarantee of the difference between the value of the solution found and the value of the optimal solution.

As with many useful but computationally complex algorithms, there has been substantial research on creating and analyzing algorithms that approximate a solution. The knapsack problem, though NP-Hard, is one of a collection of algorithms that can still be approximated to any specified degree. This means that the problem has a polynomial time approximation scheme. To be exact, the knapsack problem has a fully polynomial time approximation scheme (FPTAS).^{[27]}

George Dantzig proposed a greedy approximation algorithm to solve the unbounded knapsack problem.^{[28]} His version sorts the items in decreasing order of value per unit of weight, . It then proceeds to insert them into the sack, starting with as many copies as possible of the first kind of item until there is no longer space in the sack for more. Provided that there is an unlimited supply of each kind of item, if is the maximum value of items that fit into the sack, then the greedy algorithm is guaranteed to achieve at least a value of .

For the bounded problem, where the supply of each kind of item is limited, the above algorithm may be far from optimal. Nevertheless, a simple modification allows us to solve this case: Assume for simplicity that all items individually fit in the sack ( for all ). Construct a solution by packing items greedily as long as possible, i.e. where . Furthermore, construct a second solution containing the first item that did not fit. Since provides an upper bound for the LP relaxation of the problem, one of the sets must have value at least ; we thus return whichever of and has better value to obtain a -approximation.

It can be shown that the average performance converges to the optimal solution in distribution at the error rate ^{[29]}

The fully polynomial time approximation scheme (FPTAS) for the knapsack problem takes advantage of the fact that the reason the problem has no known polynomial time solutions is because the profits associated with the items are not restricted. If one rounds off some of the least significant digits of the profit values then they will be bounded by a polynomial and 1/ε where ε is a bound on the correctness of the solution. This restriction then means that an algorithm can find a solution in polynomial time that is correct within a factor of (1-ε) of the optimal solution.^{[27]}

algorithmFPTASisinput:ε ∈ (0,1] a list A of n items, specified by their values, , and weightsoutput:S' the FPTAS solution P := max // the highest item value K := εforifrom1tondo:=end forreturnthe solution, S', using the values in the dynamic program outlined above

**Theorem:** The set computed by the algorithm above satisfies , where is an optimal solution.

Quantum approximate optimization algorithm (QAOA) can be employed to solve Knapsack problem using quantum computation by minimizing the Hamiltonian of the problem. The Knapsack Hamiltonian is constructed via imbedding the constraint condition to the cost function of the problem with a penalty term.^{[30]}where is the penalty constant which is determined by case-specific fine-tuning.

Solving the unbounded knapsack problem can be made easier by throwing away items which will never be needed. For a given item , suppose we could find a set of items such that their total weight is less than the weight of , and their total value is greater than the value of . Then cannot appear in the optimal solution, because we could always improve any potential solution containing by replacing with the set . Therefore, we can disregard the -th item altogether. In such cases, is said to **dominate** . (Note that this does not apply to bounded knapsack problems, since we may have already used up the items in .)

Finding dominance relations allows us to significantly reduce the size of the search space. There are several different types of dominance relations,^{[11]} which all satisfy an inequality of the form:

, and for some

where and . The vector denotes the number of copies of each member of .

- Collective dominance
- The -th item is
**collectively dominated**by , written as , if the total weight of some combination of items in is less than*w*and their total value is greater than_{i}*v*. Formally, and for some , i.e. . Verifying this dominance is computationally hard, so it can only be used with a dynamic programming approach. In fact, this is equivalent to solving a smaller knapsack decision problem where , , and the items are restricted to ._{i} - Threshold dominance
- The -th item is
**threshold dominated**by , written as , if some number of copies of are dominated by . Formally, , and for some and . This is a generalization of collective dominance, first introduced in^{[19]}and used in the EDUK algorithm. The smallest such defines the**threshold**of the item , written . In this case, the optimal solution could contain at most copies of . - Multiple dominance
- The -th item is
**multiply dominated**by a single item , written as , if is dominated by some number of copies of . Formally, , and for some i.e. . This dominance could be efficiently used during preprocessing because it can be detected relatively easily. - Modular dominance
- Let be the
*best item*, i.e. for all . This is the item with the greatest density of value. The -th item is**modularly dominated**by a single item , written as , if is dominated by plus several copies of . Formally, , and i.e. .

There are many variations of the knapsack problem that have arisen from the vast number of applications of the basic problem. The main variations occur by changing the number of some problem parameter such as the number of items, number of objectives, or even the number of knapsacks.

This variation changes the goal of the individual filling the knapsack. Instead of one objective, such as maximizing the monetary profit, the objective could have several dimensions. For example, there could be environmental or social concerns as well as economic goals. Problems frequently addressed include portfolio and transportation logistics optimizations.^{[31]}^{[32]}

As an example, suppose you ran a cruise ship. You have to decide how many famous comedians to hire. This boat can handle no more than one ton of passengers and the entertainers must weigh less than 1000 lbs. Each comedian has a weight, brings in business based on their popularity and asks for a specific salary. In this example, you have multiple objectives. You want, of course, to maximize the popularity of your entertainers while minimizing their salaries. Also, you want to have as many entertainers as possible.

In this variation, the weight of knapsack item is given by a D-dimensional vector and the knapsack has a D-dimensional capacity vector . The target is to maximize the sum of the values of the items in the knapsack so that the sum of weights in each dimension does not exceed .

Multi-dimensional knapsack is computationally harder than knapsack; even for , the problem does not have EPTAS unless PNP.^{[33]} However, the algorithm in^{[34]} is shown to solve sparse instances efficiently. An instance of multi-dimensional knapsack is sparse if there is a set for such that for every knapsack item , such that and . Such instances occur, for example, when scheduling packets in a wireless network with relay nodes.^{[34]} The algorithm from^{[34]} also solves sparse instances of the multiple choice variant, multiple-choice multi-dimensional knapsack.

The IHS (Increasing Height Shelf) algorithm is optimal for 2D knapsack (packing squares into a two-dimensional unit size square): when there are at most five squares in an optimal packing.^{[35]}

This variation is similar to the Bin Packing Problem. It differs from the Bin Packing Problem in that a subset of items can be selected, whereas, in the Bin Packing Problem, all items have to be packed to certain bins. The concept is that there are multiple knapsacks. This may seem like a trivial change, but it is not equivalent to adding to the capacity of the initial knapsack. This variation is used in many loading and scheduling problems in Operations Research and has a Polynomial-time approximation scheme.^{[36]}

The quadratic knapsack problem maximizes a quadratic objective function subject to binary and linear capacity constraints.^{[37]} The problem was introduced by Gallo, Hammer, and Simeone in 1980,^{[38]} however the first treatment of the problem dates back to Witzgall in 1975.^{[39]}

The subset sum problem is a special case of the decision and 0-1 problems where each kind of item, the weight equals the value: . In the field of cryptography, the term *knapsack problem* is often used to refer specifically to the subset sum problem. The subset sum problem is one of Karp's 21 NP-complete problems.^{[40]}

A generalization of subset sum problem is called multiple subset-sum problem, in which multiple bins exist with the same capacity. It has been shown that the generalization does not have an FPTAS.^{[41]}

In the geometric knapsack problem, there is a set of rectangles with different values, and a rectangular knapsack. The goal is to pack the largest possible value into the knapsack.^{[42]}

- Bin packing problem – Mathematical and computational problem
- Change-making problem – Choosing the fewest coins to make a given amount of money
- Combinatorial auction – smart market in which participants can place bids on combinations of discrete items, rather than individual items or continuous quantities
- Combinatorial optimization – Subfield of mathematical optimization
- Continuous knapsack problem
- Cutting stock problem – Mathematical problem in operations research
- Knapsack auction
- List of knapsack problems
- Packing problem – Problems which attempt to find the most efficient way to pack objects into containers

**^**Mathews, G. B. (25 June 1897). "On the partition of numbers" (PDF).*Proceedings of the London Mathematical Society*.**28**: 486–490. doi:10.1112/plms/s1-28.1.486.**^**Kellerer, Hans; Pferschy, Ulrich; Pisinger, David (2004).*Knapsack problems*. Berlin: Springer. p. 449. ISBN 978-3-540-40286-2. Retrieved 5 May 2022.**^**Kellerer, Hans; Pferschy, Ulrich; Pisinger, David (2004).*Knapsack problems*. Berlin: Springer. p. 461. ISBN 978-3-540-40286-2. Retrieved 5 May 2022.**^**Kellerer, Hans; Pferschy, Ulrich; Pisinger, David (2004).*Knapsack problems*. Berlin: Springer. p. 465. ISBN 978-3-540-40286-2. Retrieved 5 May 2022.**^**Kellerer, Hans; Pferschy, Ulrich; Pisinger, David (2004).*Knapsack problems*. Berlin: Springer. p. 472. ISBN 978-3-540-40286-2. Retrieved 5 May 2022.**^**Feuerman, Martin; Weiss, Harvey (April 1973). "A Mathematical Programming Model for Test Construction and Scoring".*Management Science*.**19**(8): 961–966. doi:10.1287/mnsc.19.8.961. JSTOR 2629127.**^**Skiena, S. S. (September 1999). "Who is Interested in Algorithms and Why? Lessons from the Stony Brook Algorithm Repository".*ACM SIGACT News*.**30**(3): 65–74. CiteSeerX 10.1.1.41.8357. doi:10.1145/333623.333627. ISSN 0163-5700. S2CID 15619060.**^**Pisinger, D. 2003. Where are the hard knapsack problems? Technical Report 2003/08, Department of Computer Science, University of Copenhagen, Copenhagen, Denmark.**^**Caccetta, L.; Kulanoot, A. (2001). "Computational Aspects of Hard Knapsack Problems".*Nonlinear Analysis*.**47**(8): 5547–5558. doi:10.1016/s0362-546x(01)00658-7.**^**J. Jooken, P. Leyman, P. De Causmaecker, A new class of hard problem instances for the 0-1 knapsack problem,*European Journal of Operational Research*, 301 (3):841-854, 2022.- ^
^{a}^{b}^{c}Poirriez, Vincent; Yanev, Nicola; Andonov, Rumen (2009). "A hybrid algorithm for the unbounded knapsack problem".*Discrete Optimization*.**6**(1): 110–124. doi:10.1016/j.disopt.2008.09.004. ISSN 1572-5286. S2CID 8820628. **^**J. Jooken, P. Leyman, P. De Causmaecker, Features for the 0-1 knapsack problem based on inclusionwise maximal solutions,*European Journal of Operational Research*, 311 (1):36-55, 2023.**^**Wojtczak, Dominik (2018). "On Strong NP-Completeness of Rational Problems".*Computer Science – Theory and Applications*. Lecture Notes in Computer Science. Vol. 10846. pp. 308–320. arXiv:1802.09465. doi:10.1007/978-3-319-90530-3_26. ISBN 978-3-319-90529-7. S2CID 3637366.**^**Dobkin, David; Lipton, Richard J. (1978). "A lower bound of ½*n*^{2}on linear search programs for the Knapsack problem".*Journal of Computer and System Sciences*.**16**(3): 413–417. doi:10.1016/0022-0000(78)90026-0.**^**In fact, the lower bound applies to the subset sum problem, which is a special case of Knapsack.**^**Michael Steele, J; Yao, Andrew C (1 March 1982). "Lower bounds for algebraic decision trees".*Journal of Algorithms*.**3**(1): 1–8. doi:10.1016/0196-6774(82)90002-5. ISSN 0196-6774.**^**Ben-Amram, Amir M.; Galil, Zvi (2001), "Topological Lower Bounds on Algebraic Random Access Machines",*SIAM Journal on Computing*,**31**(3): 722–761, doi:10.1137/S0097539797329397.**^**auf der Heide, Meyer (1984), "A Polynomial Linear Search Algorithm for the*n*-Dimensional Knapsack Problem",*Journal of the ACM*,**31**(3): 668–676, doi:10.1145/828.322450- ^
^{a}^{b}Andonov, Rumen; Poirriez, Vincent; Rajopadhye, Sanjay (2000). "Unbounded Knapsack Problem : dynamic programming revisited".*European Journal of Operational Research*.**123**(2): 168–181. CiteSeerX 10.1.1.41.2135. doi:10.1016/S0377-2217(99)00265-9. **^**S. Martello, P. Toth, Knapsack Problems: Algorithms and Computer Implementations, John Wiley and Sons, 1990**^**S. Martello, D. Pisinger, P. Toth, Dynamic programming and strong bounds for the 0-1 knapsack problem,*Manag. Sci.*, 45:414–424, 1999.**^**Plateau, G.; Elkihel, M. (1985). "A hybrid algorithm for the 0-1 knapsack problem".*Methods of Oper. Res*.**49**: 277–293.**^**Martello, S.; Toth, P. (1984). "A mixture of dynamic programming and branch-and-bound for the subset-sum problem".*Manag. Sci*.**30**(6): 765–771. doi:10.1287/mnsc.30.6.765.**^**Horowitz, Ellis; Sahni, Sartaj (1974), "Computing partitions with applications to the knapsack problem",*Journal of the Association for Computing Machinery*,**21**(2): 277–292, doi:10.1145/321812.321823, hdl:1813/5989, MR 0354006, S2CID 16866858**^**Nederlof, Jesper; Węgrzycki, Karol (12 April 2021). "Improving Schroeppel and Shamir's Algorithm for Subset Sum via Orthogonal Vectors". arXiv:2010.08576 [cs.DS].**^**Schroeppel, Richard; Shamir, Adi (August 1981). "A $T = O(2^{n/2} )$, $S = O(2^{n/4} )$ Algorithm for Certain NP-Complete Problems".*SIAM Journal on Computing*.**10**(3): 456–464. doi:10.1137/0210033. ISSN 0097-5397.- ^
^{a}^{b}Vazirani, Vijay. Approximation Algorithms. Springer-Verlag Berlin Heidelberg, 2003. **^**Dantzig, George B. (1957). "Discrete-Variable Extremum Problems".*Operations Research*.**5**(2): 266–288. doi:10.1287/opre.5.2.266.**^**Calvin, James M.; Leung, Joseph Y. -T. (1 May 2003). "Average-case analysis of a greedy algorithm for the 0/1 knapsack problem".*Operations Research Letters*.**31**(3): 202–210. doi:10.1016/S0167-6377(02)00222-5.**^**Lucas, Andrew (2014). "Ising formulations of many NP problems".*Frontiers in Physics*.**2**: 5. arXiv:1302.5843. Bibcode:2014FrP.....2....5L. doi:10.3389/fphy.2014.00005. ISSN 2296-424X.**^**Chang, T. J., et al. Heuristics for Cardinality Constrained Portfolio Optimization. Technical Report, London SW7 2AZ, England: The Management School, Imperial College, May 1998**^**Chang, C. S., et al. "Genetic Algorithm Based Bicriterion Optimization for Traction Substations in DC Railway System." In Fogel [102], 11-16.**^**Kulik, A.; Shachnai, H. (2010). "There is no EPTAS for two dimensional knapsack" (PDF).*Inf. Process. Lett*.**110**(16): 707–712. CiteSeerX 10.1.1.161.5838. doi:10.1016/j.ipl.2010.05.031.- ^
^{a}^{b}^{c}Cohen, R. and Grebla, G. 2014. "Multi-Dimensional OFDMA Scheduling in a Wireless Network with Relay Nodes". in*Proc. IEEE INFOCOM'14*, 2427–2435. **^**Yan Lan, György Dósa, Xin Han, Chenyang Zhou, Attila Benkő [1]:*2D knapsack: Packing squares*, Theoretical Computer Science Vol. 508, pp. 35–40.**^**Chandra Chekuri and Sanjeev Khanna (2005). "A PTAS for the multiple knapsack problem".*SIAM Journal on Computing*.**35**(3): 713–728. CiteSeerX 10.1.1.226.3387. doi:10.1137/s0097539700382820.**^**Wu, Z. Y.; Yang, Y. J.; Bai, F. S.; Mammadov, M. (2011). "Global Optimality Conditions and Optimization Methods for Quadratic Knapsack Problems".*J Optim Theory Appl*.**151**(2): 241–259. doi:10.1007/s10957-011-9885-4. S2CID 31208118.**^**Gallo, G.; Hammer, P. L.; Simeone, B. (1980). "Quadratic knapsack problems".*Combinatorial Optimization*. Mathematical Programming Studies. Vol. 12. pp. 132–149. doi:10.1007/BFb0120892. ISBN 978-3-642-00801-6.**^**Witzgall, C. (1975). "Mathematical methods of site selection for Electronic Message Systems (EMS)".*NASA Sti/Recon Technical Report N*.**76**. NBS Internal report: 18321. Bibcode:1975STIN...7618321W.**^**Richard M. Karp (1972). "Reducibility Among Combinatorial Problems". In R. E. Miller and J. W. Thatcher (editors). Complexity of Computer Computations. New York: Plenum. pp. 85–103**^**Caprara, Alberto; Kellerer, Hans; Pferschy, Ulrich (2000). "The Multiple Subset Sum Problem".*SIAM J. Optim*.**11**(2): 308–319. CiteSeerX 10.1.1.21.9826. doi:10.1137/S1052623498348481.**^**Galvez, Waldo; Grandoni, Fabrizio; Ingala, Salvatore; Heydrich, Sandy; Khan, Arindam; Wiese, Andreas (2021). "Approximating Geometric Knapsack via L-packings".*ACM Trans. Algorithms*: 33:1–33:67. arXiv:1711.07710. doi:10.1145/3473713.

- Garey, Michael R.; David S. Johnson (1979).
*Computers and Intractability: A Guide to the Theory of NP-Completeness*. W.H. Freeman. ISBN 978-0-7167-1045-5. A6: MP9, pg.247. - Kellerer, Hans; Pferschy, Ulrich; Pisinger, David (2004).
*Knapsack Problems*. Springer. doi:10.1007/978-3-540-24777-7. ISBN 978-3-540-40286-2. MR 2161720. S2CID 28836720. - Martello, Silvano; Toth, Paolo (1990).
*Knapsack problems: Algorithms and computer implementations*. Wiley-Interscience. ISBN 978-0-471-92420-3. MR 1086874.

- GitHub repository containing hard 0-1 knapsack problem instances
- GitHub repository containing features for identifying what makes a 0-1 knapsack problem instance hard
- Lecture slides on the knapsack problem
- PYAsUKP: Yet Another solver for the Unbounded Knapsack Problem, with code taking advantage of the dominance relations in an hybrid algorithm, benchmarks and downloadable copies of some papers.
- Home page of David Pisinger with downloadable copies of some papers on the publication list (including "Where are the hard knapsack problems?")
- Knapsack Problem solutions in many languages at Rosetta Code
- Dynamic Programming algorithm to 0/1 Knapsack problem
- Knapsack Problem solver (online)
- Solving 0-1-KNAPSACK with Genetic Algorithms in Ruby Archived 23 May 2011 at the Wayback Machine
- Codes for Quadratic Knapsack Problem Archived 14 February 2015 at the Wayback Machine