A Behind the Scenes look at InfiniDB: Ease of Use (Part 3 of 3)

Jim Tommaney, Chief Technology Officer, Calpont

This post is the third in a three-part series covering InfiniDB's hallmark characteristics: I/O efficiency, parallelism and ease-of-use.

When we set out to design InfiniDB, we wanted to build a database that was extremely easy-to-use.


Read more ...

A Behind the Scenes look at InfiniDB: Parallelism (Part 2 of 3)

Jim Tommaney, Chief Technology Officer, Calpont

As part of a second post in our three-part series, we'd like to discuss the importance of parallelism and how InfiniDB uses parallelism to achieve breath taking performance.

InfiniDB is architected for effortless scalability.

The InfiniDB


Read more ...

A Behind the Scenes look at InfiniDB (Part 1 of 3)

Jim Tommaney, Chief Technology Officer, Calpont

Since the launch of InfiniDB last year, we've been seeing InfiniDB enabling tremendous customer successes. We've seen hundreds of customers use InfiniDB to power their most impactful analytics projects.

We’d like to describe InfiniDB's


Read more ...

InfiniDB to 1 Trillion Rows ( 1,039,909,436,172 )

Jim Tommaney, Chief Technology Officer, Calpont

Calpont's InfiniDB has hit a new milestone, loading over 1 trillion rows with our columnar analytics DBMS with the actual value being 1039909436172 rows.  As expected, the load rate is stable over the entire duration, loading better than 1.1 million rows per second. 
InfiniDB Load Rate Trended trhough 1 Trillion Rows

The size of source files was 20195.94GB, size on disk was 5657.52GB.  Special thanks to Chris Wolf, Auburn '14 for execution of this benchmark.  Additional details to follow including query performance and a breakdown on compression. 
Let us help you put your data to work.  - Jim Tommaney CTO, Calpont. 


Read more ...

Calpont is pleased to announce high performance sub-query support

Calpont is pleased to announce high performance sub-query support with the latest alpha version (1.1.2) of InfiniDB. We’re especially happy about this release because polls done by MySQL have consistently shown – year after year – that slow


Read more ...