Showing posts from May, 2015

Kronometrix Analytics Appliance: Xen vs ESXi

Latest Update: Tue May  5 15:54:10 EEST 2015

We heavily use Redis as part of our Kronometrix analytics software. For those which do not know what Redis is, see here.

Recently we have upgraded our kernel from Redis 2.8.x branch to 3.x, latest release. And we were curious to see what sort of improvements and how latest Redis release works for our application in regard with ESXi and Xen. As already said, KronometrixAppliance can works as a:
physical appliance, operating system + analytics software on bare metalvirtual appliance, running as one or many virtual machines within Xen or ESXi We are planning to check the redis-server proces utilization, extract a stack trace for the redis-server on both hypervisors.

Generic X86_64 Server Ubuntu Server 12.04.5 LTS, Xen 4.2.2 amd64 1 x Intel(R) Core(TM) i7 CPU 930 @ 2.80GHz Hyperthreading: Available, ON 24 GB RAM 1 TB internal storage for dom0, 2TB NAS for domU

We have configured dom0 to boot and have 2 assigned vCPUs and 6 GB RAM:  GRUB_CMDLINE_…

The Appliance ...

Our analytic software, Kronometrix, runs on top of an operating system, tuned and configured for data analysis, bundled as a ready image, which can be downloaded and installed. The idea is simple, we wanted to offer something which is already tested, tuned and configured for hundreds, thousands of data sources. We call this, the Kronometrix Appliance and we want it to be ready to:
work with or without WAN connectionwork on batteries and solar panelshandle large or small volume of data in real-timeanalyse data from different data sources, different industrieshave zero-administration and no maintenancebe affordable Memory it's the new hard disk 
Another PHP or Java application on top of MySQL ? Or maybe PostgreSQL ? Right ? Boringggg.

When we started Kronometrix, we basically cleaned the table and we wanted to see things aligned for future not 1978. The first thing, was where to store all the time series data and how to access that. And we went full speed into the future: a NoSQL da…