Académique Documents
Professionnel Documents
Culture Documents
MySQL intro
Kickfire background
Technology overview
Demo
Customer case studies
Q&A
MySQL intro
Kickfire background
Technology overview
Demo
Customer case studies
Q&A
MySQL intro
Kickfire background
Technology overview
Demo
Customer case studies
Q&A
Technical issues
• Reports and queries take too long to run
• Lots of tuning and maintenance necessary
• Difficulty supporting ad-hoc queries or complex reports
Business impact
• Difficulty in growing the system with the business
• Too much time, money, and effort spent on maintenance
• Value for business and for customers limited
MySQL intro
Kickfire background
Technology overview
Demo
Customer case studies
Q&A
• Yes
• No
• No, but plan to
SQL: MOPS Query Parallelization SQC operates directly SQC uses column-
= done on SINGLE SQC out of Memory, NOT store, compression,
drastically reducing limited by Registers intell indexes and pre-
1:10 h/w footprint fetches from storage
Database
Memory
Unified
Host x86
Memory x86
Storage
Array
Unified Dataflow
Database Engine
Memory
(SQL Chip)
1. SQL execution 1.
1. Connectivity
Optimizer
2. Memory management 2.
2. Security
Column store & cache
3. Loader acceleration 3.
3. Administration
Transactional engine
MySQL
KDB
Setup
• Pre-configured appliance to deliver high performance on broad set
of schemas and queries
2000 Series
• Size: 2 RU
• Capacity: up to 0.8TB
• Power use: ~600 W
• Price: starting at ~$20k
3000 Series
• Size: 3 RU
• Capacity: up to 3TB
• Power use: ~700 W
• Price: starting at ~$65k
• 1GB - 49GB
• 50GB – 99GB
• 100GB – 999GB
• 1TB – 5TB
• > 5TB
MySQL intro
Kickfire background
Technology overview
Demo
Customer case studies
Q&A
Customer
• Public company with large online communities
Problems
• Canned reports are too slow and report development too slow
because need too many aggregate tables
• Can’t create a new revenue service based on ad hoc queries
Customer environment
• 1 TB MySQL DW with multiple customer DB of clickstream data
• Two dual-CPU servers with 16GB RAM
Kickfire system
• Kickfire Database Appliance 2200 with 32GB RAM
© 2008 Kickfire, Inc. All rights reserved.
Customer Case Study #1: Results
Customer
• Successful high-tech startup in network management domain
Problems
• Can’t scale to larger data volumes of network data
• Revenue tied to scaling of network monitoring service
Customer environment
• Up to 1 TB DW of customer network data
Kickfire system
• Kickfire Database Appliance 2300 with 64GB RAM
Additional information
• Product is currently in beta; program currently oversubscribed
• If interested in trials, please email sales@kickfire.com
• For more info, download our white paper and data sheet
Stay in touch
• Read our blog www.kickfire.com/blog
• Send us an email info@kickfire.com
• Call us at 408.450.5400
σσp2(c,d)
ππ p2(c,d)
T2.d
σσ σσ
p1(a,b)
p1(a,b)
p1(a,b)
p1(a,b)
T2.c
σσ p0(a)
p0(a)
σσ
p0(a)
p0(a)
Answer is
returned
through
MySQL
MySQL
Optimizer &
execution is
by-passed
Parsed
query is
intercepted
by KDB &
executed in
Chip
KDB
Storage
Source: MySQL 5.0 Pluggable Storage Engine Architecture document
Engine
© 2008 Kickfire, Inc. All rights reserved.
Typical Features in DW Queries
Select Many columns; Complex expressions; Aggregations;
Proj. Optimization
From In-line-views (Subselect)