Fast Counting in Machine Learning Applications

04/12/2018 ∙ by Subhadeep Karan, et al. ∙ University at Buffalo 0

We propose scalable methods to execute counting queries in machine learning applications. To achieve memory and computational efficiency, we abstract counting queries and their context such that the counts can be aggregated as a stream. We demonstrate performance and scalability of the resulting approach on random queries, and through extensive experimentation using Bayesian networks learning and association rule mining. Our methods significantly outperform commonly used ADtrees and hash tables, and are practical alternatives for processing large-scale data.



There are no comments yet.


page 7

This week in AI

Get the week's most popular data science and artificial intelligence research sent straight to your inbox every Saturday.

1 Introduction

Counting data records with instances that support some specific configuration of the selected variables is one of the basic operations utilized by machine learning (ML) algorithms. For example, when learning Bayesian network structure from data counting is necessary to evaluate a scoring function, or to assess constraints (e.g., via mutual information) [1]. In association rule mining, counting over binary data representing transactions is required to assess support and confidence for a given association rule [2]. Other examples include problems ranging from classification [3, 4]

through deep learning 

[5, 6] to information retrieval [7].

While counting is typically viewed as a black-box procedure, and implemented using simple and not necessarily efficient strategies, e.g., contingency tables, in many practical applications it accounts for over 90% of the total execution time (we show several practical cases in Sec. 

4). Consequently, improving performance of counting can directly translate into better performance of these applications. At the same time, popular specialized approaches based on data indexes, such as ADtrees [8], have limited applicability due to the significant preprocessing and memory overheads, which easily exceed the capability of current computational servers. This holds true for a broad spectrum of problem sizes and applications, with cases involving anywhere from tens to hundreds of variables, and thousands to millions of instances. As the size of the data analyzed by ML codes increases, there is a clear need for easy-to-adopt, efficient and scalable counting strategies.

In this paper, we address the above challenge by designing simple, yet fast and memory efficient counting strategies. Our methods are derived from the standard techniques like bitmap set representation and radix sorting, which can be efficiently implemented in a software. We describe an intuitive and convenient programming interface that leverages properties of the operators used in ML to separate the counting process from how the counts are utilized. This interface enables us to aggregate counts in a stream-like fashion. We encapsulate our methods in an open source software, and demonstrate its performance on random queries, Bayesian networks learning and association rule mining. Through extensive experiments on multiple popular benchmark data, we show that our strategies are orders of magnitude faster than the commonly used methods, such as ADtrees and hash tables.

2 Preliminaries

Consider a set of

categorical random variables

, where the domain of variable is represented by states . Alternatively, we can think of as a symbolic feature with arity , and for convenience we can represent its states by integers . Let be a complete database of instances of , where , , records observed states of . Given , and a set of input variables , the counting query returns the size of the support in for the specific assignment of variables . For example, for the database in Fig. 1, the query would return , as there are instances matching the query condition. We note that the above formulation of counting is a special and simple case of the general counting problem in conjunctive queries, known from database theory [9] (we provide more details in Section 5).

Counting queries are the basic operations performed when learning statistical models from data. In some ML applications, such as association rule mining or learning probabilistic graphical models, they may account for over 90% of the total execution time. In the most basic form, the queries can be issued without shared context. For example, to estimate joint probability

from , we could use just one query: . However, in the most common use scenarios, a group of consecutive queries is executed over the same set of variables (i.e., the queries share context). For instance, consider log-likelihood score frequently used in Bayesian networks learning [10]:



is a set of predictor variables for

,  enumerates all possible states of variables in , and and are respectively the counts of instances in such that variables in are in state , and the counts of instances such that variables in are in state and is in state . To compute we require multiple counting queries over the same group of variables , testing different configurations of their states. Moreover, we care only about queries that return non-zero counts (note that non-zero implies non-zero ), since only those contribute to the final sum.

The standard approach to handle queries that share context is to either directly scan the database to construct contingency table of counts (or its high-dimensional variant such as data cube [11]), or to first create an ADtree index to cache all sufficient statistics from , and then to materialize contingency table on demand. Here materialization is done by retrieving the required counts via fast traversal over the index [8, 12]. However, both these approaches have significant limitations.

To use a contingency table we have to either maintain a lookup table with entries, or to use a dictionary (e.g., hash table) with keys over the states of

and values being vectors of counts for the corresponding states of

. While lookup table may offer very fast memory accesses during construction and querying phases, it becomes computationally impractical, since usually it is very sparse. This is because even for large , most of the time will not contain all possible configurations for the majority of sets . Consequently, lookup tables become a feasible choice only when we are dealing with a small number of variables, each with very small arity. Dictionaries address the problem of sparsity, as they store only configurations that are observed in . However, they impose non-trivial overheads owing to the cost of hashing in a hash table dictionary or traversing scattered memory in a search tree dictionary. Moreover, when large number of high-arity variables are considered, a dictionary quickly becomes memory intensive easily exceeding capacity of a typical cache memory.

The alternative approach is to use one of many published variants of the ADtree index, e.g., [8, 12, 13, 14]. Here the idea is to first invest (significant) time and memory to enumerate and cache counts of all configurations found in , and then reference those counts to answer subsequent queries. However, even with various optimizations, the space complexity of ADtrees is exponential in the number of variables, and even for modestly sized it may exceed the available main memory. Moreover, by caching all counts indiscriminately, ADtrees often store entries that are never referenced in a given application, creating unnecessary memoization and searching overhead. Finally, ADtrees still require that a contingency table is materialized to deliver retrieved counts, and hence they pose a significant challenge in balancing memory and computations.

3 Proposed Approach

Given the database , our goal is to provide memory and computationally efficient mechanism to answer counting queries with shared context. The memory efficiency is critical, since many ML algorithms, especially in classification and probabilistic graphical modeling, already have significant memory constraints (see for example [15]). If the memory has to be devoted to handling queries instead of being used by the actual algorithm, it would clearly constrain the applicability of the algorithm. At this point it is worth noting that ML applications fall into a gray zone in terms of the size of the input data on which they typically operate. On the one hand, the size of the input is too small to benefit from many excellent optimizations known from database theory (some we review in Sec. 5), as those are targeting cases in which volume of the data necessitates concurrent use of both persistent and main memory. On the other hand, the data is too large to warrant efficient execution using direct techniques like simple contingency tables.

To address this situation, we first define an intuitive programming interface to abstract the query context, including how counts are utilized by the target application. Then, we overlay the interface on top of two simple, yet very efficient, query execution strategies, where instead of storing counts we consume them in a stream-like fashion.

Figure 1: (a) Database with three variables, and the corresponding bitmap representation of . (b) Example of executing over using Bitmap strategy, and (c) Radix strategy.
1class L {
3  void operator()(int Nijk, int Nij) {
4    double p = 1.0 * Nijk / Nij;
5    score_ += (Nijk * log2(p));
6  }
7  double score() const { return score_; }
9  double score_ = 0.0;
Figure 2: Example C++ code packaging Eq. (1) into our programming interface.

3.1 Programming Interface

In a typical application, counts provided by queries with shared context are iteratively aggregated via some associative and commutative operator. One simple example with the summation operator is given in Eq. (1). A more complex example could be Dirichlet priors with the product of gamma functions [16]

. From the computational point of view, this assumption is very helpful as it provides ample opportunities for optimization. We note also that while it may look very narrow, it actually accurately captures surprisingly many ML applications, which primarily involve estimating conditional probabilities. Examples include classifiers and regression, feature extraction, different variants of probabilistic graphical models, etc..

Following notation in Sec. 2, let us consider a set of variables and their corresponding counts and , for some specific configuration of and of . Here we are distinguishing between counts for and to simplify computing conditional probabilities while maintaining generality – by passing we can execute queries over single variable , and by considering only we get joint queries . The key observation is that we can leverage associativity and commutativity, and instead of first gathering all counts and then performing aggregation, we can create a stream of counts corresponding to all unique and relevant configurations found in , and perform the aggregation directly on the stream. This enables us to push computations to data, mitigating memory overheads due to counts caching. To achieve this, we abstract the computations via a function object (a concept supported by all modern programming languages), which is then repeatedly invoked over the stream. The example function object corresponding to Eq. (1) is given in Fig. 2. In the essence, the object receives and via the function call operator (line 3), performs the required intermediate computations, and then aggregates the result into internal state. This internal state can be then inspected (line 7) to retrieve the final result of the aggregation. From the user perspective, the function call operator acts as an interface, and is directly invoked by a routine responsible for enumerating, and emitting, all unique configurations for the variables of interest (see parameter in Algs. 1 and 2 in the following sections). Thus the interface provides a convenient encapsulation, and the end-user who defines the function object (e.g., implementing a scoring function in BN learning) can focus solely on expressing computations (i.e., high-level logic and correctness), and does not have to worry about potentially complex logic of low-level details (e.g., how counts are enumerated). Additionally, because function object behaves like a function, but has the advantage of possessing an internal state, it is a convenient mechanism to express even the most demanding computations.

While the proposed interface stems from a relatively simple observation, it has several immediate advantages. First, by separating functionality (i.e., data traversing from computations) we gain flexibility to rapidly investigate different data traversal schemes to extract counts, or even alternate between different strategies depending on the query context (e.g., how many variables are involved, their domain, etc.). Second, since counts are aggregated into an isolated state represented by a function object, and multiple objects can coexist independently, multiple groups of queries, each group with individual context, can be executed concurrently and in parallel, e.g., by different threads. Collectively, this makes the proposed design extremely flexible, efficient and easy to use, as we demonstrate in the experimental results section.

3.2 Bitmap Strategy

For the specific and our task now is to enumerate counts and for all configurations and found in , and then pass the counts to a function object for aggregation. The idea behind the Bitmap strategy is to represent each variable via a set of bitmaps of size , where each bitmap indicates instances for which is in the corresponding state (see Fig. 1a). Then, the entire process of enumerating counts can be reduced to performing logical and on bitmaps, equivalent of set intersection, and to bit counting, equivalent of computing set cardinality. This is summarized in Alg. 1, with example in Fig. 1b (for convenience, in the algorithm we use set notation instead of directly representing bitmaps).

1   if  then
3      for  do
6          if  then
7                 emit new configuration
8   else
10      for  do
12          if  then
Algorithm 1

To execute counting queries for and (abbreviated to ), and function object , we perform Depth First Traversal (DFS) over the tree whose leaves represent all possible states of interest (recall that ). The bottom layer of the tree is induced by the states of , and the top layers correspond to variables in . When moving down the tree (lines 9-13), we compute intersection between the set of instances supporting variables’ configurations seen thus far (in the algorithm denoted by , which initially consists of all instances), and the set of instances supporting current configuration of the considered variable from (in the algorithm denoted by ). We continue traversal only if the size of the intersection is greater than zero, implying non-zero count for given joint configuration of variables. Once we reach a leaf of the tree (lines 1-7), we compute the final counts and for the corresponding configurations and , and emit those via call to .

The depth of the tree depends on the number of variables involved in the query, and the number of leaves is bounded by , with each step in the traversal involving cost of computing intersection and cardinality. While the tree could potentially involve exponential (in the number of query variables) number of nodes, it is never explicitly stored in the memory, and even for with large number of instances many configurations have zero count, allowing for their corresponding sub-trees to be pruned. To further leverage this property, we order such that variables with lowest entropy estimated from are at the top of the tree. Since variables with low entropy are likely to have configurations for which there will be only few supporting instances, they are more likely to trigger zero counts and hence lead to a smaller tree to traverse. For example, consider executing outlined in Fig. 1b. There are total of configurations which we should enumerate, and if we traverse the tree starting from variable , which has lower entropy than , then we will have to consider intermediate states. If we were to start with variable , then this number would increase to . This optimization performs extremely well in practice, and, as we show in the experimental results section, for certain ranges of and , Bitmap outperforms other strategies.

In the practical terms, the strategy can be efficiently implemented using streaming extensions (SIMD) in current processors. Bitmaps for individual variables can be precomputed and laid out in the memory instead of , with acceptable memory overhead (i.e., vs. bits), and the relative ordering of variables in , based on their entropy, can be established beforehand as well.

3.3 Radix Strategy

While the Bitmap strategy is amenable to very efficient implementation, its scalability may still suffer when datasets with very large number of instances are exercised by queries with many variables, or variables with high arity. This is because in such cases the DFS tree will have fewer nodes to prune, and the advantage of fast bit-wise operations will be offset by the poor asymptotic behavior. To address these cases, we consider an alternative approach, which we refer to as Radix strategy. The strategy is derived from the classic radix sort algorithm, and it involves recursively partitioning instances in such that single partition at given level captures all instances corresponding to one specific configuration of the query variables. This approach is summarized in Algs. 2 and 3, with example in Fig. 1c.

2   if  then
4   for  do
6      if  then
8          for  do
10             if  then
11                    emit new configuration
Algorithm 2
2   for  do
5   if  then
6      return  
8   for  do
10   return  
Algorithm 3 Buckets(, , )

The algorithm follows the Most Significant Digit (MSD) radix, with the left most digits being states of individual variables in , and the least significant digit representing states of  (Alg. 2, line 3). At each level, the number of newly created partitions is proportional to the arity of the considered variable, and the size of the partition is the support in for the particular configuration. The order in which variables from are processed is not significant, since the cost of identifying empty partitions does not induce overheads. Because the actual instances in are not to be sorted, but only partitioned, it is sufficient that we maintain a list (in algorithms denoted by ) of partition descriptors containing indexes of the constituent instances and partition size (Alg. 3, lines 1-4). As soon as all partitions prescribed by are identified we can proceed to emitting counts (Alg. 2, lines 4-11), which must be preceded by the final round of partitioning with respect to (Alg. 2, line 7).

The algorithm requires that for each variable its corresponding data vector is completely scanned, leading to the overall complexity. In practice, the entire method is efficiently implemented by first organizing the database in the column-major format, and then maintaining a FIFO queue of partition descriptors, with auxiliary space to keep track of the assignment of indexes to partitions. Moreover, partitioning for individual variables can be precomputed in advance, further bootstrapping the first step of the algorithm.

To conclude the presentation, we note that both Bitmap and Radix strategies can be further augmented such that instead of enumerating all counts (i.e., executing queries with shared context) they deliver counts just for the specific assignment of the query variables. To achieve this, it is sufficient to process only a single path from the root to the leaf with the target assignment in the DFS tree of the Bitmap strategy, and to find the partition corresponding to the assignment, instead of all partitions, in Radix.

4 Experimental Validation

We implemented both proposed strategies as a C++ software library, which we complemented with Python bindings for the ease of use. At its core, the library uses standard SSE SIMD intrinsics to implement basic bitmap operations (i.e., logical and, and bit counting), and it exposes all functionality via the interface described in Sec. 3.1. The resulting open source package, which we call SABNAtk, is available from:

We deployed SABNAtk on a server with two Intel Xeon E5-2650 2.30 GHz 10-core CPUs, and 64 GB of RAM. To test the performance, we ran a series of experiments using popular ML benchmark datasets (see data summary in Tab. 1). For reference, we used hash table from the C++ standard library, and the sparse ADtree data index [8]. The hash table represented contingency table created by directly scanning the input database, with keys encoding specific assignment of variables in , and values representing vectors of counts for specific assignment of . To maximize cache memory usage, the strategy operated on the database stored in the row-major order. Finally, to make the comparison fair and avoid biases due to the differences in programming languages, we developed an efficient ADtree implementation in C++. We note that other available implementations, for example [17], turned out to be substantially slower than our version.

Dataset Range of Average
Child 20 2-6 3
Insur(ance) 27 2-5 3.3
Mild(ew) 35 3-99 16.4
Alarm 37 2-4 2.83
Barley 46 3-67 9.02
Hail(finder) 56 2-11 3.98
Win95(pts) 74 2-2 2
Path(finder) 104 2-63 4.2
Table 1: Benchmark data used in experiments.
Child Alarm Hail
Figure 3: Comparison ADT, Hash, BMap and Rad strategies on the stream of uniformly random queries. The plots show the distribution of response time in microseconds, computed from the same sample of 1,000 queries for different number of instances . Y-axis is in log-scale.

In the following, we discuss in detail several key results obtained using the above setup. More extensive results (including additional test cases), together with the data that can be used to reproduce our experiments, are available from:

Before we proceed with the results discussion, we note that in order to use ADtree, the input database has to be first indexed. In all our experiments, we considered only the query time with index already loaded into memory. Moreover, ADtree provides a hyper-parameter to configure the size of the leaf-lists [8]. We experimented with several values of the parameter, to fine-tune the trade-off between query performance and memory consumption, and we settled with , which we use throughout the paper. The results obtained for other ADtree configurations exhibited similar patterns to those reported in the paper, and are available online.

4.1 Random Queries

In the first set of experiments we tested how ADtree (ADT), HashTable (Hash), Bitmap (BMap), and Radix (Rad) strategies respond to a stream of random queries. The idea here is to understand average performance of each strategy in case where we have no prior information about specific query execution patterns. For each benchmark database, we generated 100,000 queries of the form as follows. First, the size of was sampled uniformly from the range , and then variables were assigned to and by randomly sampling without replacement from

. To measure time taken to execute the query, we used a simple function object that consumes and immediately discards the counts. In this way, the overhead of performing computations on the counts was negligible, and did not offset the actual time spent by each strategy to enumerate the counts. Each query was executed five times to obtain the average response time (with negligible variance), and exactly the same stream of queries was processed by each strategy. The results of this experiment are summarized in Figs. 

3 and 4. Here, we note that plots are in scale, and should be interpreted with care.

Figure 4: Comparison of ADT, Hash, BMap, and Rad for different sizes of (x-axis) in the sample of 1,000 uniformly random queries. The plot shows the average query response time in microseconds. Y-axis is in log-scale.

Figure 3 shows that depending on the number of input variables , and the number of instances , different strategies perform better in terms of the mean response time. When the number of instances is relatively small, Bitmap strategy significantly outperforms other methods. This is explained by two factors: first, for small scale data, Bitmap benefits from continuous memory accesses, and acceleration via SIMD instructions, second, because in small datasets many possible variable configurations are unobserved, Bitmap is able to prune significant portions of the DFS tree, taking advantage of the entropy-based data reordering (see Sec. 3.2). However, as the number of instances in the input database increases these advantages diminish, to the extent where the average time taken by a query becomes unacceptable (longer than several seconds, a threshold we set to make experiments computationally feasible). The Radix and HashTable strategies perform steadily across all datasets, and are able to handle even the most demanding test cases. This is expected, since both strategies involve similar data access pattern (i.e., scanning selected columns of the input database). However, Rad is on average 20 times faster than Hash (not captured in the figure due to log-scale), as it does not require costly hashing and scattered memory accesses.

The ADtree strategy exhibits the best mean response for problems with few variables and large number of instances, but it significantly underperforms in all remaining test cases. In fact, as the number of variables increases, ADtree fails to index the database and cannot be used to answer the queries. This is because the exponential growth of the number of configurations, which have to be cached, leads to the exhaustion of the main memory. Recall also that we do not include ADtree preprocessing time, which for datasets with more than 100K instances exceeds several hours, much longer than the time required to answer all 100K queries.

To further dissect performance of random queries, in Fig. 4 we show how the response time varies with the number of query variables, for an example database. When processing small queries (), ADtree is generally outperformed by BMap, and when handling large queries () it is slower than Rad. Moreover, the cost of Radix strategy is linear with the query size, compared to the exponential growth of ADtree.

Based on the tests with random queries, we conclude that Bitmap and Radix strategies significantly outperform ADtree and HashTable, except of a small set of scenarios in which small queries are executed over databases with few variables and millions of instances, if we exclude the preprocessing time.

4.2 Queries in Bayesian Networks Learning

Counting queries with shared context are the key operations performed in score-based Bayesian networks structure learning and Markov blankets discovery [1]. Both problems depend on the parent set assignment as a sub-routine [18], and for given can be solved exactly by traversing a lattice with levels formed by the partial order set inclusion on the power set of . For given and , queries of the form are performed for each , where iterates over all possible subsets of , starting from empty set. Hence, at level we have that , and there are total queries to execute, creating interesting pattern of queries that grow in size as computations progress. The function object implements decomposable scoring function, e.g., MDL [19], BDeu [16], etc., that evaluates the assignment of  as parents of .

We used all tested strategies to implement counting queries in the open source parent set assignment solver [20]. The solver uses MDL scoring function, deploys several optimizations to eliminate some of the queries based on the results seen thus far, and because it effectively explores large combinatorial search space it has significant memory requirements. It also leverages OpenMP to execute multiple queries in parallel. As such, it serves as a practical benchmark for the query strategies. In our experiments, instead of considering all possible parent set sizes, as required by the exact solver, we limited the solver to

, to make tests computationally feasible. This corresponds to a heuristic in which we make an assumption that no variable in the final Bayesian network can have more than six parents.

Figure 5: The total execution time of the parent set assignment solver with ADT, Hash, BMap and Rad strategies, normalized with respect to the fastest method. The solver was executed up to the level where .

Figure 5 shows the total execution time of the solver for different input databases and query strategies. From the plots, we can see that our proposed strategies significantly outperform ADtree and HashTable, across all benchmarks. In fact, for datasets with high-arity variables, i.e., Mildew and Barley, the Radix strategy is 100 times faster than ADtree. This is explained by very large number of states that are to be expected in such datasets (and are costly to manage by ADtree), and by the pattern of how queries are generated by the solver. Because the size of the queries and their number grow together, there are only a few small queries that benefit ADtree, and increasing number of queries that are easily handled by the Radix strategy.

To illustrate how critical is the performance of counting queries for parent sets assignment, in Tab. 2 we report the total execution time of the solver, together with the fraction of the time taken by the queries, when running on databases with 100K instances. In all cases, the execution is dominated by database querying that accounts for 90%-99% of the total time. Interestingly, this fraction is smaller for ADtree than for other strategies, even though ADtree is slower (we observed this pattern in all test cases). We believe that this is because BMap and Rad are memory friendly, and have minimal effect on memory utilization by the solver, thus minimizing cache update overheads, which in turn could slow down the solver. This is not the case for ADtree, which requires gigabytes of memory to run, and hence influences performance of the solver, affecting the ratio between the query and the solver time.

Insur Mild Alarm Barley
ADT 35m20s 119m
Hash 26m26s 92m3s 190m47s 276m16s
BMap 17m28s 1107m57s 100m55s
Rad 4m41s 37m28s 43m4s 156m32s
Table 2: Execution time of the parent set assignment.

4.3 Queries in Association Rule Mining

Association rule mining is the classic method for establishing implication rules between a set of items in a database [2, 21]

. Given a set of binary variables

, and a database of transactions , where shows in which transactions item represented by was involved (i.e., is in state ), we want to identify rules of the form with support, i.e., how frequently are set together in , and confidence, i.e., how frequently the rule is true in , above some predefined thresholds. In the most direct form, the problem can be solved by traversing the power set lattice over , a query pattern similar to the one used by the parent set assignment solver. However, compared to the parent set assignment, the actual queries are simpler, since we only require the counts of query variables being in state . For example, to assess the rule we would perform queries and . Consequently, instead of considering the query context, it is sufficient that our strategies search for one specific configuration of the query variables (as explained at the end of Sec. 3.3).

We used all four tested strategies to implement simple association rule mining engine based on the bottom-up search [21]. With the engine, we processed several large databases to enumerate rules with the support above and confidence above , but of size less than seven. We selected these thresholds empirically to retrieve association rules with more than four variables, which allowed us to reliably measure the execution times (for smaller rules, the solver ran extremely fast). Results of this experiment are summarized in Fig. 6.

Figure 6: The total execution time of association rule mining with ADT, Hash, BMap and Rad strategies, normalized with respect to the fastest method. The solver was executed up to the level where .

The figure shows that the Bitmap strategy significantly outperforms other approaches across all tested databases. Since in the Bitmap, processing queries with specific assignment amounts to a series of bitmap intersections, followed by bit counting, the cost of queries becomes linear in the size of the query and the number of instances in the database. Moreover, because all bit-wise operations are implemented via SIMD extensions, BMap becomes much faster than Rad, which has the same asymptotic behavior but involves less cache friendly operations. Finally, the overheads of traversing ADtree and handling its MCV subtrees (see [12] for details) leads to its poor overall performance. At this point we should note that originally ADtree was designed for learning of association rules, however the design did not account for the memory and SIMD capabilities of modern processors.

5 Related Work

As we mentioned through out the paper, counting queries in machine learning applications are often handled via some variant of the ADtree data index. The sparse ADtree [8, 12], which we used in our experiments, precomputes and caches counts for all possible variable configurations. The counts are organized into a tree of vary nodes, encoding the choice of variables to facilitate fast searching, and AD nodes that store the actual query counts. To partially mitigate the excessive memory use, ADtrees do not explicitly represent most commonly occurring counts, and instead of creating AD nodes for counts lower than certain threshold, they resort to on-demand counting when such nodes are accessed. These base ideas have been extended by multiple researchers to account for dynamic data (i.e., updates to the database) [22], and to improve performance on high-arity data [13, 14]. However, as the core functionality in these data structures remains exactly the same, they suffer from the same limitations that we demonstrated in our experiments (expensive preprocessing, large memory footprint, significant traversing overheads).

Support for counting queries is a primary component in any database management system. In such systems, the query mechanism must support conjunctive queries over multiple tables, and with a variety of possible query predicates [9]. Moreover, the queries are typically executed over tables that cannot be fully materialized in the main memory. Our Bitmap strategy can be viewed as a practical realization of the Leapfrog Trie Join [23] with an unary relation, under assumption that the entire database resides in the main memory.

The idea of using bitmaps to represent sets and their operations (e.g., intersection, cardinality, etc.) is frequent in software and databases design. This is because it allows to reduce memory, storage or network bandwidth, while maintaining the basic sets functionality [24]. In these applications, bitmaps are typically compressed following methods like for example RLE encoding or Roaring [25, 26]. The compressed bitmaps are orthogonal to our approach, and in fact we could use them to improve memory profile of our Bitmap strategy. However, as the compression induces computational overheads, and the size of the databases we consider practical is relatively small, currently we do not use compression.

6 Conclusions

In this paper, we describe efficient strategies for handling counting queries in machine learning applications. By combining convenient programming interface with memory efficient data traversing algorithms we are able to scale to large data instances, which we confirm via extensive experiments. The proposed solutions outperform and can substitute popular ADtree index. Moreover, to maintain best possible performance across different data instances, they can be selectively applied at the runtime depending on the properties of the queries.

While our approach is presented as a method for static databases, we note that it can be easily adopted to the cases where the input database expands with new instances during processing. This would amount to a simple update to the bitmaps in the Bitmap strategy, and is automatically handled in the Radix strategy.


Authors wish to acknowledge hardware and technical support provided by the Center for Computational Research at the University at Buffalo. This work has been supported in part by the Department of Veterans Affairs under grant 7D0084, and by the National Institutes of Health under grant 1UL1 TR001412-01.


  • [1] D. Koller and N. Friedman, Probabilistic Graphical Models: Principles and Techniques.   MIT Press, 2009.
  • [2] R. Agrawal, T. Imielinski, and A. Swami, “Mining association rules between sets of items in large databases,” in ACM SIGMOD International Conference on Management of Data, vol. 22, no. 2, 1993, pp. 207–216.
  • [3]

    R. Kohavi, “Scaling up the accuracy of Naive-Bayes classifiers: A decision-tree hybrid,” in

    International Conference on Knowledge Discovery and Data Mining, 1996, pp. 202–207.
  • [4] J. Quinlan, “Bagging, boosting, and C4.5,” in

    AAAI Innovative Applications of Artificial Intelligence Conferences

    , 1996, pp. 725–730.
  • [5]

    H. Lee, R. Grosse, R. Ranganath, and A. Ng, “Convolutional deep belief networks for scalable unsupervised learning of hierarchical representations,” in

    International Conference on Machine Learning.   ACM, 2009, pp. 609–616.
  • [6]

    R. Salakhutdinov and G. Hinton, “Deep Boltzmann machines,” in

    International Conference on Artificial Intelligence and Statistics, 2009, pp. 448–455.
  • [7] J. Ramos, “Using TF-IDF to determine word relevance in document queries,” in Instructional Conference on Machine Learning, 2003, pp. 133–142.
  • [8] A. Moore and M. Lee Soon, “Cached sufficient statistics for efficient machine learning with large datasets,” Journal of Artificial Intelligence Research, vol. 8, pp. 67–91, 1998.
  • [9] G. Greco and F. Scarcello, “Counting solutions to conjunctive queries,” in ACM Symposium on Principles of Database Systems, 2014, pp. 132–143.
  • [10] L. de Campos, “A scoring function for learning Bayesian networks based on mutual information and conditional independence tests,” Journal of Machine Learning Research, vol. 7, pp. 2149–2187, 2006.
  • [11] J. Han, J. Pei, and M. Kamber, Data Mining: Concepts and Techniques.   Morgan Kaufmann Publishers, 2011.
  • [12] B. Anderson and A. Moore, “ADtrees for fast counting and for fast learning of association rules,” in Conference on Knowledge Discovery and Data Mining, 1998.
  • [13] R. van Dam, I. Langkilde-Geary, and D. Ventura, “Adapting ADtrees for high arity features,” in AAAI Conference on Artificial Intelligence, 2008.
  • [14] ——, “Adapting ADtrees for improved performance on large datasets with high-arity features,” Knowledge and Information Systems, vol. 35, 2013.
  • [15] C. Yuan, B. Malone, and X. Wu, “Learning optimal Bayesian networks using A* search,” in International Joint Conference on Artificial Intelligence, 2011, pp. 2186–2191.
  • [16] G. Cooper and E. Herskovits, “A Bayesian method for the induction of probabilistic networks from data,” Machine Learning, vol. 9, no. 4, pp. 309–347, 1992.
  • [17] “Sparse AD-Tree package in Python,”
  • [18] M. Koivisto, “Parent assignment is hard for the MDL, AIC, and NML costs,” in

    International Conference on Computational Learning Theory

    , 2006, pp. 289–303.
  • [19] G. Schwarz, “Estimating the dimension of a model,” The Annals of Statistics, vol. 6, pp. 461–464, 1978.
  • [20] “SABNA – Scalable Accelerated Bayesian Network Analytics,”
  • [21] M. Zaki, “Scalable algorithms for association mining,” IEEE Transactions on Knowledge and Data Engineering, vol. 12, no. 3, pp. 372–390, 2000.
  • [22] J. Roure and A. Moore, “Sequential update of ADtrees,” in International Conference on Machine Learning, 2006, pp. 769–776.
  • [23] T. Veldhuizen, “Leapfrog triejoin: A simple, worst-case optimal join algorithm,” arXiv preprint arXiv:1210.0481, 2012.
  • [24] O. Kaser and D. Lemire, “Compressed bitmap indexes: Beyond unions and intersections,” Software: Practice and Experience, vol. 46, no. 2, pp. 167–198, 2016.
  • [25] D. Lemire, O. Kaser, and K. Aouiche, “Sorting improves word-aligned bitmap indexes,”

    Data and Knowledge Engineering

    , vol. 69, no. 1, pp. 3–28, 2010.
  • [26] D. Lemire, O. Kaser, N. Kurz, L. Deri, C. O’Hara, F. Saint-Jacques, and G. Ssi-Yan-Kai, “Roaring bitmaps: Implementation of an optimized software library,” Software: Practice and Experience, vol. 48, no. 4, pp. 867–895, 2018.