Indexes are an essential tool for optimizing database performance and are becoming ever more important with big data. However, as the volume of data increases, index maintenance often becomes a write bottleneck, especially for advanced index types which use a lot of CPU time for every row that gets written. Index creation may also become prohibitively expensive as it may take hours or even days to build a new index on terabytes of data in postgres. As of Citus 6.0, we’ve made creating and maintaining indexes that much faster through parallelization.

Citus can be used to distribute PostgreSQL tables across many machines. One of the many advantages of Citus is that you can keep adding more machines with more CPUs such that you can keep increasing your write capacity even if indexes are becoming the bottleneck. As of Citus 6.0 CREATE INDEX can also be performed in a massively parallel fashion, allowing fast index creation on large tables. Moreover, the COPY command can write multiple rows in parallel when used on a distributed table, which greatly improves performance for use-cases which can use bulk ingestion (e.g. sensor data, click streams, telemetry).

To show the benefits of parallel indexing, we’ll walk through a small example of indexing ~200k rows containing large JSON objects from the GitHub archive. To run the examples, we set up a formation using Citus Cloud consisting of 4 worker nodes with 4 cores each, running PostgreSQL 9.6 with Citus 6.

You can download the sample data by running the following commands:

wget http://examples.citusdata.com/github_archive/github_events-2015-01-01-{0..24}.csv.gz gzip -d github_events-*.gz

Next lets create the table for the GitHub events once as a regular PostgreSQL table and then distribute it across the 4 nodes:

CREATE TABLE github_events ( event_id bigint, event_type text, event_public boolean, repo_id bigint, payload jsonb, repo jsonb, actor jsonb, org jsonb, created_at timestamp ); -- (distributed table only) Shard the table by repo_id SELECT create_distributed_table('github_events', 'repo_id'); -- Initial data load: 218934 events from 2015-01-01 \COPY github_events FROM PROGRAM 'cat github_events-*.csv' WITH (FORMAT CSV)

Each event in the GitHub data set has a detailed payload object in JSON format. Building a GIN index on the payload gives us the ability to quickly perform fine-grained searches on events, such as finding commits from a specific author. However, building such an index can be very expensive. Fortunately, parallel indexing makes this a lot faster by using all cores at the same time and building many smaller indexes:

CREATE INDEX github_events_payload_idx ON github_events USING GIN ( payload );

| | Regular table | Distributed table | Speedup | |---------------------------|---------------|-------------------|---------| | CREATE INDEX on 219k rows | 33.2s | 2.6s | 13x |

To test how well this scales we took the opportunity to run our test multiple times. Interestingly, parallel CREATE INDEX exhibits superlinear speedups giving >16x speedup despite having only 16 cores. This is likely due to the fact that inserting into one big index is less efficient than inserting into a small, per-shard index (following O(log N) for N rows), which gives an additional performance benefit to sharding.

| | Regular table | Distributed table | Speedup | |---------------------------|---------------|-------------------|---------| | CREATE INDEX on 438k rows | 55.9s | 3.2s | 17x | | CREATE INDEX on 876k rows | 110.9s | 5.0s | 22x | | CREATE INDEX on 1.8M rows | 218.2s | 8.9s | 25x |

Once the index is created, the COPY command also takes advantage of parallel indexing. Internally, COPY sends a large number of rows over multiple connections to different workers asynchronously which then store and index the rows in parallel. This allows for much faster load times than a single PostgreSQL process could achieve. How much speedup depends on the data distribution. If all data goes to the a single shard, performance will be very similar to PostgreSQL.

\ COPY github_events FROM PROGRAM 'cat github_events-*.csv' WITH ( FORMAT CSV )

| | Regular table | Distributed table | Speedup | |-------------------------|---------------|-------------------|---------| | COPY 219k rows no index | 18.9s | 12.4s | 1.5x | | COPY 219k rows with GIN | 49.3s | 12.9s | 3.8x |

Finally, it’s worth measuring the effect that the index has on query time. We try two different queries, one across all repos and one with a specific repo_id filter. This distinction is relevant to Citus because the github_events table is sharded by repo_id . A query with a specific repo_id filter goes to a single shard, whereas the other query is parallelised across all shards.

On 219k rows, this gives us the query times below. Times marked with * are of queries that are executed in parallel by Citus. Parallelisation creates some fixed overhead, but also allows for more heavy lifting, which is why it can either be much faster or a bit slower than queries on a regular table.

| | Regular table | Distributed table | |---------------------------------------|---------------|-------------------| | SELECT no indexes, all repos | 900ms | 68ms* | | SELECT with GIN on payload, all repos | 2ms | 11ms* | | SELECT no indexes, single repo | 900ms | 28ms | | SELECT with indexes, single repo | 2ms | 2ms |

Indexes in PostgreSQL can dramatically reduce query times, but at the same time dramatically slow down writes. Citus gives you the possibility of scaling out your cluster to get good performance on both sides of the pipeline. A particular sweet spot for Citus is parallel ingestion and single-shard queries, which gives querying performance that is better than regular PostgreSQL, but with much higher and more scalable write throughput.

If you would like to learn more about parallel indexes or other ways in which Citus helps you scale, consult our documentation or give us a ping on slack. You can also get started with Citus in minutes by downloading Citus open source to spin up a cluster on your desktop, or by deploying Citus in the cloud.