Tag: performance

MongoDB fails to perform, runs out of gas

MongoDB fails to perform, runs out of gas

Is performance still a problem for MongoDB? Avalon benchmarked Couchbase Server and MongoDB last year, and a lot has changed since then. Couchbase Server 4.0 introduced a SQL-based query language, N1QL. Couchbase Server 4.1 added prepared statements and covering indexes,...

Using Covering Indexes on a Multiple Document Type Bucket

Using Covering Indexes on a Multiple Document Type Bucket

I was recently working on a project that made use of N1QL for querying Couchbase Server data. This was an internal Java application that I was hosting on a low budget Amazon EC2 instance. My problem here is that my...

Often Overlooked Linux OS Tweaks

Often Overlooked Linux OS Tweaks

There are two simple linux OS level settings that people seem to be overlooking setting correctly on their production systems I have seen. These are documented elsewhere, but they keep coming up and seems like they need some quick review...

Prepared Statements – by the Numbers!

Prepared Statements – by the Numbers!

Always be Prepared…. In our last discussion on prepared statements in couchbase we talked about the performance gains that are possible using prepared statements. I thought I’d post a “sequel” with a few real world examples and numbers using the...

February 4, 2016
Prepare for This!

Prepare for This!

Get Prepared…. One of the more impressive aspects of using N1QL is the ability to use prepared statements. What are prepared statements? Why use them? What’s the big deal? Consider the following example from the travel-sample bucket and dataset that are bundled...

February 4, 2016
Indexes for N1QL: or how I got an order magnitude speed increase

Indexes for N1QL: or how I got an order magnitude speed increase

Indexes for N1QL: or how I got an order magnitude speed increase In Couchbase 4.0 we introduced N1QL query language: a flexible query language that brings SQL-like query to JSON documents. Whenever we talk about N1QL the conversation always opens...

MongoDB and DataStax, In the Rearview Mirror

MongoDB and DataStax, In the Rearview Mirror

Thumbtack published an excellent blog post today (link). It highlights the preliminary results of performance tests executed with Couchbase Server, MongoDB and DataStax Enterprise (Apache Cassandra). The final results will be included in a benchmark report. Thumbtack consulted with Couchbase,...

DataStax FUD

DataStax FUD

This is not the first time I've addressed FUD (link). However, it is the first time I've addressed FUD directed at Couchbase and that's a great thing. After all, I know what happens next. First they ignore you, then they...

Dissecting the NoSQL Benchmark

Dissecting the NoSQL Benchmark

Let's dissect the Fall 2014 NoSQL Benchmark. Apache Cassandra / DataStax Enterprise. MongoDB. Couchbase Server. Go. Hardware   Server (8) Client (32) Processor Intel Xeon E5-2620 V2 (2) Intel Core i5-4440 Memory 64GB 8GB Storage (Data) 100GB SATA 6Gb/s SSD...

Caching queries in Couchbase for high performance

Caching queries in Couchbase for high performance

Starting from version 2.0, Couchbase server offers a powerful way of creating indexes for JSON documents through the concept of views.   Using views, it is possible to define primary indexes, composite indexes and aggregations allowing to: . query documents...

December 16, 2014
MongoDB and Apache Cassandra / DataStax, where art thou?

MongoDB and Apache Cassandra / DataStax, where art thou?

Today, Thumbtack Technology published a blog post highlighting the final results of the NoSQL benchmark (link). In June, the databases were benchmarked on 4 physical servers. I could see MongoDB and DataStax in the rearview mirror (link). Then, the databases...

Performance: Managing threads in Couchbase 2.x

Performance: Managing threads in Couchbase 2.x

In this blog post you will get an overview of two related performance optimizations that you can do for Couchbase 2.5.1 and below. This is not for 3.x for reasons you can read at the bottom of this post. The two changes...