Presented at Percona Live Amsterdam 2016, this is an in-depth look at MariaDB Server right up to MariaDB Server 10.1. Learn the differences. See what's already in MySQL. And so on.
Maria DB Galera Cluster for High AvailabilityOSSCube
Want to understand how to set high availability solutions for MySQL using MariaDB Galera Cluster? Join this webinar, and learn from experts. During this webinar, you will also get guidance on how to implement MariaDB Galera Cluster.
MySQL Administrator
Basic course
- MySQL 개요
- MySQL 설치 / 설정
- MySQL 아키텍처 - MySQL 스토리지 엔진
- MySQL 관리
- MySQL 백업 / 복구
- MySQL 모니터링
Advanced course
- MySQL Optimization
- MariaDB / Percona
- MySQL HA (High Availability)
- MySQL troubleshooting
네오클로바
http://neoclova.co.kr/
MariaDB: in-depth (hands on training in Seoul)Colin Charles
MariaDB: in-depth is training that was conducted for partners selling/deploying MariaDB in Seoul. Its a practical hands-on introduction that can be completed in 1-day.
The presentation covers improvements made to the redo logs in MySQL 8.0 and their impact on the MySQL performance and Operations. This covers the MySQL version still MySQL 8.0.30.
Running MariaDB in multiple data centersMariaDB plc
MariaDB is often deployed in multiple data centers for high availability and/or disaster recovery. Tim Tadeo, Senior Sales Engineer, walks through real-world use cases and the topologies customers have created to leverage multiple data centers. He also discusses important considerations and how to address them, as well as more advanced options such as dedicated binlog servers for cross–data center replication.
Demystifying the Distributed Database Landscape (DevOps) (1).pdfScyllaDB
What is the state of high-performance, distributed databases as we head deeper into 2022, and which options are best suited for your own development projects?
The data-intensive applications leading this next tech cycle are typically powered by multiple types of databases and data stores—each satisfying specific needs and often interacting with a broader data ecosystem. Even the very notion of a database is evolving as new hardware architectures and methodologies allow for ever-greater capabilities and expectations for horizontal and vertical scalability, performance and reliability.
In this webinar, Peter Corless, ScyllaDB’s director of technology advocacy, will survey the current landscape of distributed database systems and highlight new directions in the industry.
This talk will cover different database and database-adjacent technologies as well as describe their appropriate use cases, patterns and anti-patterns with a focus on:
- Distributed SQL, NewSQL and NoSQL
- In-memory datastores and caches
- Streaming technologies with persistent data storage
Maria DB Galera Cluster for High AvailabilityOSSCube
Want to understand how to set high availability solutions for MySQL using MariaDB Galera Cluster? Join this webinar, and learn from experts. During this webinar, you will also get guidance on how to implement MariaDB Galera Cluster.
MySQL Administrator
Basic course
- MySQL 개요
- MySQL 설치 / 설정
- MySQL 아키텍처 - MySQL 스토리지 엔진
- MySQL 관리
- MySQL 백업 / 복구
- MySQL 모니터링
Advanced course
- MySQL Optimization
- MariaDB / Percona
- MySQL HA (High Availability)
- MySQL troubleshooting
네오클로바
http://neoclova.co.kr/
MariaDB: in-depth (hands on training in Seoul)Colin Charles
MariaDB: in-depth is training that was conducted for partners selling/deploying MariaDB in Seoul. Its a practical hands-on introduction that can be completed in 1-day.
The presentation covers improvements made to the redo logs in MySQL 8.0 and their impact on the MySQL performance and Operations. This covers the MySQL version still MySQL 8.0.30.
Running MariaDB in multiple data centersMariaDB plc
MariaDB is often deployed in multiple data centers for high availability and/or disaster recovery. Tim Tadeo, Senior Sales Engineer, walks through real-world use cases and the topologies customers have created to leverage multiple data centers. He also discusses important considerations and how to address them, as well as more advanced options such as dedicated binlog servers for cross–data center replication.
Demystifying the Distributed Database Landscape (DevOps) (1).pdfScyllaDB
What is the state of high-performance, distributed databases as we head deeper into 2022, and which options are best suited for your own development projects?
The data-intensive applications leading this next tech cycle are typically powered by multiple types of databases and data stores—each satisfying specific needs and often interacting with a broader data ecosystem. Even the very notion of a database is evolving as new hardware architectures and methodologies allow for ever-greater capabilities and expectations for horizontal and vertical scalability, performance and reliability.
In this webinar, Peter Corless, ScyllaDB’s director of technology advocacy, will survey the current landscape of distributed database systems and highlight new directions in the industry.
This talk will cover different database and database-adjacent technologies as well as describe their appropriate use cases, patterns and anti-patterns with a focus on:
- Distributed SQL, NewSQL and NoSQL
- In-memory datastores and caches
- Streaming technologies with persistent data storage
The webinar will review a multi-layered framework for PostgreSQL security, with a deeper focus on limiting access to the database and data, as well as securing the data.
Using the popular AAA (Authentication, Authorization, Auditing) framework we will cover:
- Best practices for authentication (trust, certificate, MD5, Scram, etc).
- Advanced approaches, such as password profiles.
- Deep dive of authorization and data access control for roles, database objects (tables, etc), view usage, row-level security, and data redaction.
- Auditing, encryption, and SQL injection attack prevention.
Note: this session is delivered in German
Speaker:
Borys Neselovskyi, Sales Engineer, EDB
Optimizing MariaDB for maximum performanceMariaDB plc
When it comes to optimizing the performance of a database, DBAs have to look at everything from the OS to the network. In this session, MariaDB Enterprise Architect Manjot Singh shares best practices for getting the most out of MariaDB. He highlights recommended OS settings, important configuration and tuning parameters, options for improving replication and clustering performance and features such as query result caching.
Introducing Galera Cluster & the Codership Team
Galera Cluster in a nutshell:
True multi-master:
Read & write to any node
* Synchronous replication
* No slave lag
* No integrity issues
* No master-slave failovers or VIP needed
* Multi-threaded slave, no performance penalty
* Automatic node provisioning
Elastic:
Easy scale-out & scale-in, all nodes read-write
There exist some valid reasons to rebuild indexes on an Oracle database (not many). This presentation is about some of those reasons and how to automate such online index rebuild.
Understanding the architecture of MariaDB ColumnStoreMariaDB plc
MariaDB ColumnStore extends MariaDB Server, a relational database for transaction processing, with distributed columnar storage and parallel query processing for scalable, high-performance analytical processing. This session helps MariaDB users understand how MariaDB ColumnStore works and why it’s needed for more demanding analytical workloads, and covers:
Use cases
Query processing
Bulk data insertion
Distributed partitions
Query optimization
Standard Edition High Availability (SEHA) - The Why, What & HowMarkus Michalewicz
Standard Edition High Availability (SEHA) is the latest addition to Oracle’s high availability solutions. This presentation explains the motivation for Standard Edition High Availability, how it is implemented and the way it works currently as well as what is planned for future improvements. It was first presented during Oracle Groundbreakers Yatra (OGYatra) Online in July 2020.
MySQL Database Architectures - MySQL InnoDB ClusterSet 2021-11Kenny Gryp
Oracle's MySQL solutions make it easy to setup various database architectures and achieve high availability with the introduction MySQL InnoDB Cluster and MySQL InnoDB ReplicaSet meeting various high availability requirements. MySQL InnoDB ClusterSet provides a popular disaster recovery solution.
Completely built in-house and supported by Oracle, many enterprises large and small have adopted these solutions into business critical applications.
In this presentation the various database architecture solutions for high availability and disaster recovery will be covered and help you choose the right solutions based on your business requirements.
MariaDB Galera Cluster Webinar by Ivan Zoratti on 13.11.2013. Also available as on demand webinar at http://www.skysql.com/why-skysql/webinars/mariadb-galera-cluster-simple-transparent-highly-available
This presentation provides a clear overview of how Oracle Database In-Memory optimizes both analytics and mixed workloads, delivering outstanding performance while supporting real-time analytics, business intelligence, and reporting. It provides details on what you can expect from Database In-Memory in both Oracle Database 12.1.0.2 and 12.2.
This was a short 25 minute talk, but we go into a bit of a history of MySQL, how the branches and forks appeared, what's sticking around today (branch? Percona Server. Fork? MariaDB Server). What should you use? Think about what you need today and what the roadmap holds.
The Proxy Wars - MySQL Router, ProxySQL, MariaDB MaxScaleColin Charles
As proxies (and database routers) go, the first one I ever used was the now deprecated MySQL Proxy. Since then, I've managed to use MariaDB MaxScale quite a bit (including its fork AirBnB MaxScale), played around with ProxySQL in recent time, and also started taking a look at MySQL Router. In this quick 20-minute overview, we'll discuss why these three exist, a feature comparison, and reasons when to use the right tool for the job.
The webinar will review a multi-layered framework for PostgreSQL security, with a deeper focus on limiting access to the database and data, as well as securing the data.
Using the popular AAA (Authentication, Authorization, Auditing) framework we will cover:
- Best practices for authentication (trust, certificate, MD5, Scram, etc).
- Advanced approaches, such as password profiles.
- Deep dive of authorization and data access control for roles, database objects (tables, etc), view usage, row-level security, and data redaction.
- Auditing, encryption, and SQL injection attack prevention.
Note: this session is delivered in German
Speaker:
Borys Neselovskyi, Sales Engineer, EDB
Optimizing MariaDB for maximum performanceMariaDB plc
When it comes to optimizing the performance of a database, DBAs have to look at everything from the OS to the network. In this session, MariaDB Enterprise Architect Manjot Singh shares best practices for getting the most out of MariaDB. He highlights recommended OS settings, important configuration and tuning parameters, options for improving replication and clustering performance and features such as query result caching.
Introducing Galera Cluster & the Codership Team
Galera Cluster in a nutshell:
True multi-master:
Read & write to any node
* Synchronous replication
* No slave lag
* No integrity issues
* No master-slave failovers or VIP needed
* Multi-threaded slave, no performance penalty
* Automatic node provisioning
Elastic:
Easy scale-out & scale-in, all nodes read-write
There exist some valid reasons to rebuild indexes on an Oracle database (not many). This presentation is about some of those reasons and how to automate such online index rebuild.
Understanding the architecture of MariaDB ColumnStoreMariaDB plc
MariaDB ColumnStore extends MariaDB Server, a relational database for transaction processing, with distributed columnar storage and parallel query processing for scalable, high-performance analytical processing. This session helps MariaDB users understand how MariaDB ColumnStore works and why it’s needed for more demanding analytical workloads, and covers:
Use cases
Query processing
Bulk data insertion
Distributed partitions
Query optimization
Standard Edition High Availability (SEHA) - The Why, What & HowMarkus Michalewicz
Standard Edition High Availability (SEHA) is the latest addition to Oracle’s high availability solutions. This presentation explains the motivation for Standard Edition High Availability, how it is implemented and the way it works currently as well as what is planned for future improvements. It was first presented during Oracle Groundbreakers Yatra (OGYatra) Online in July 2020.
MySQL Database Architectures - MySQL InnoDB ClusterSet 2021-11Kenny Gryp
Oracle's MySQL solutions make it easy to setup various database architectures and achieve high availability with the introduction MySQL InnoDB Cluster and MySQL InnoDB ReplicaSet meeting various high availability requirements. MySQL InnoDB ClusterSet provides a popular disaster recovery solution.
Completely built in-house and supported by Oracle, many enterprises large and small have adopted these solutions into business critical applications.
In this presentation the various database architecture solutions for high availability and disaster recovery will be covered and help you choose the right solutions based on your business requirements.
MariaDB Galera Cluster Webinar by Ivan Zoratti on 13.11.2013. Also available as on demand webinar at http://www.skysql.com/why-skysql/webinars/mariadb-galera-cluster-simple-transparent-highly-available
This presentation provides a clear overview of how Oracle Database In-Memory optimizes both analytics and mixed workloads, delivering outstanding performance while supporting real-time analytics, business intelligence, and reporting. It provides details on what you can expect from Database In-Memory in both Oracle Database 12.1.0.2 and 12.2.
This was a short 25 minute talk, but we go into a bit of a history of MySQL, how the branches and forks appeared, what's sticking around today (branch? Percona Server. Fork? MariaDB Server). What should you use? Think about what you need today and what the roadmap holds.
The Proxy Wars - MySQL Router, ProxySQL, MariaDB MaxScaleColin Charles
As proxies (and database routers) go, the first one I ever used was the now deprecated MySQL Proxy. Since then, I've managed to use MariaDB MaxScale quite a bit (including its fork AirBnB MaxScale), played around with ProxySQL in recent time, and also started taking a look at MySQL Router. In this quick 20-minute overview, we'll discuss why these three exist, a feature comparison, and reasons when to use the right tool for the job.
Lessons from {distributed,remote,virtual} communities and companiesColin Charles
A last minute talk for the people at DevOps Amsterdam, happening around the same time as O'Reilly Velocity Amsterdam 2016. Here are lessons one can learn from distributed/remote/virtual communities and companies from someone that has spent a long time being remote and distributed.
Securing your MySQL / MariaDB Server dataColin Charles
Co-presented alongside Ronald Bradford, this covers MySQL, Percona Server, and MariaDB Server (since the latter occasionally can be different enough). Go thru insecure practices, focus on communication security, connection security, data security, user accounts and server access security.
Best practices for MySQL/MariaDB Server/Percona Server High AvailabilityColin Charles
Best practices for MySQL/MariaDB Server/Percona Server High Availability - presented at Percona Live Amsterdam 2016. The focus is on picking the right High Availability solution, discussing replication, handling failure (yes, you can achieve a quick automatic failover), proxies (there are plenty), HA in the cloud/geographical redundancy, sharding solutions, how newer versions of MySQL help you, and what to watch for next.
Forking Successfully - or is a branch better?Colin Charles
Forking Successfully or do you think a branch will work better? Learn from history, see what's current, etc. Presented at OSCON London 2016. This is forking beyond the github generation. And if you're going to do it, some tips on how you could be successful.
Presented at the MySQL Chicago Meetup in August 2016. The focus of the talk is on backups and verification, replication and failover, as well as security and encryption.
MariaDB Server Compatibility with MySQLColin Charles
At the MariaDB Server Developer's meeting in Amsterdam, Oct 8 2016. This was the deck to talk about what MariaDB Server 10.1/10.2 might be missing from MySQL versions up to 5.7. The focus is on compatibility of MariaDB Server with MySQL.
Failure happens, and we can learn from it. We need to think about backups, but also verification of them. We should definitely make use of replication and think about automatic failover. And security is key, but don't forget that encryption is now available in MySQL, Percona Server and MariaDB Server.
MariaDB 10.1 what's new and what's coming in 10.2 - Tokyo MariaDB MeetupColin Charles
Presented at the Tokyo MariaDB Server meetup in July 2016, this is an overview of what you can see and use in MariaDB Server 10.1, but more importantly what is planned to arrive in 10.2
MariaDB - the "new" MySQL is 5 years old and everywhere (LinuxCon Europe 2015)Colin Charles
MariaDB is like the "new" MySQL, and its available everywhere. This talk was given at LinuxCon Europe in Dublin in October 2015. Learn about all the new features, considering the release was just around the corner. Changes in replication are also very interesting
This is my third iteration of the talk presented in Tokyo, Japan - first was at a keynote at rootconf.in in April 2016, then at the MySQL meetup in New York, and now for dbtechshowcase. The focus is on database failures of the past, and how modern MySQL / MariaDB Server technologies could have helped them avoid such failure. The focus is on backups and verification, replication and failover, and security and encryption.
Hexatier - MySQL Role-based Security & Data MaskingScott Uhrick
Presentation given at New York MySQL Meetup, Sept 8 2016. Covers how we use Hexatier at Teladoc to provide role-based security and to mask PHI in the database.
MariaDB started life as a database to host the Maria storage engine in 2009. Not long after its inception, the MySQL community went through yet another change in ownership, and it was deemed that MariaDB will be a complete database branch developed to extend MySQL, but with constant merging of upstream changes.
The goal of the MariaDB project is to ensure that everyone is part of the community, including employees of the major steering companies. MariaDB also features enhanced features, some of which are common with the Percona Performance Server. Most importantly, MariaDB is a drop-in replacement and is completely backward compatible with MySQL. In 2010, MariaDB released 5.1 in February, and 5.2 in November – two major releases in a span of one calendar year is a feat that was achieved!
DBAs and developers alike will gain an introduction to MariaDB, what is different with MySQL, how to make use of the feature enhancements, and more.
Meet MariaDB Server 10.1 London MySQL meetup December 2015Colin Charles
Meet MariaDB Server 10.1, the server that got released recently. Presented at the London MySQL Meetup in December 2015. Learn about the new features in MariaDB Server, especially around the focus of what we did to improve security.
Meet MariaDB 10.1 at the Bulgaria Web SummitColin Charles
Meet MariaDB 10.1 at the Bulgaria Web Summit, held in Sofia in February 2016. Learn all about MariaDB Server, and the new features like encryption, audit plugins, and more.
An introduction to MongoDB from an experienced MySQL user and developer. There are differences and we go thru the What/Why/Who/Where of MongoDB, the "similarities" to the MySQL world like storage engines, how replication is a little more interesting with built-in sharding and automatic failover, backups, monitoring, DBaaS, going to production and finding out more resources.
MySQL is a unique adult (now 21 years old) in many ways. It supports plugins. It supports storage engines. It is also owned by Oracle, thus birthing two branches of the popular opensource database: Percona Server and MariaDB Server. It also once spawned a fork: Drizzle. Lately a consortium of web scale users (think a chunk of the top 10 sites out there) have spawned WebScaleSQL.
You're a busy DBA having to maintain a mix of this. Or you're a CIO planning to choose one branch. How do you go about picking? Supporting multiple databases? Find out more in this talk. Also covered is a deep-dive into what feature differences exist between MySQL/Percona Server/MariaDB/WebScaleSQL, how distributions package the various databases differently. Within the hour, you'll be informed about the past, the present, and hopefully be knowledgeable enough to know what to pick in the future.
Note, there will also be coverage of the various trees around WebScaleSQL, like the Facebook tree, the Alibaba tree as well as the Twitter tree.
MariaDB - Fast, Easy & Strong - Get Started Tutorialphamhphuc
MariaDB - Fast, Easy & Strong - Get Started Guide. You can understand why you should use MariaDB and how easy to install it for your server. Let 's enjoy!!!
The MySQL ecosystem - understanding it, not running away from it! Colin Charles
You're a busy DBA thinking about having to maintain a mix of this. Or you're a CIO planning to choose one branch over another. How do you go about picking? Supporting multiple databases? Find out more in this talk. Also covered is a deep-dive into what feature differences exist between MySQL/Percona Server/MariaDB Server. Within 20 minutes, you'll leave informed and knowledgable on what to pick.
A base blog post to get started: https://www.percona.com/blog/2017/11/02/mysql-vs-mariadb-reality-check/
Today you can use hosted MySQL/MariaDB/Percona Server in several "cloud providers" in what is considered using it as a service, a database as a service (DBaaS). You can also use hosted PostgreSQL and MongoDB thru various service providers. Learn the differences, the access methods, and the level of control you have for the various public cloud offerings:
- Amazon RDS for MySQL and PostgreSQL
- Google Cloud SQL
- Rackspace OpenStack DBaaS
- The likes of compose.io, MongoLab and Rackspace's offerings around MongoDB
The administration tools and ideologies behind it are completely different, and you are in a "locked-down" environment. Some considerations include:
* Different backup strategies
* Planning for multiple data centres for availability
* Where do you host your application?
* How do you get the most performance out of the solution?
* What does this all cost?
Growth topics include:
* How do you move from one DBaaS to another?
* How do you move all this from DBaaS to your own hosted platform?
Questions like this will be demystified in the talk. This talk will benefit experienced database administrators (DBAs) who now also have to deal with cloud deployments as well as application developers in startups that have to rely on "managed services" without the ability of a DBA.
MariaDB 10: A MySQL Replacement - HKOSC Colin Charles
MariaDB 10: A MySQL Replacement. Current up to 10.0.9, right before the 10.0.10 GA release presented the weekend before the release in Hong Kong, at the Hong Kong Open Source Conference.
Differences between MariaDB 10.3 & MySQL 8.0Colin Charles
MySQL and MariaDB are becoming more divergent. Learn what is different from a high level. It is also a good idea to ensure that you use the correct database for the correct job.
MariaDB - a MySQL Replacement #SELF2014Colin Charles
MariaDB - a MySQL replacement at South East Linux Fest 2014 - SELF2014. Learn about features that are not in MySQL 5.6, some that are only just coming in MySQL 5.7, and some that just don't exist.
You want to use MySQL in Amazon RDS, Rackspace Cloud, Google Cloud SQL or HP Helion Public Cloud? Check this out, from Percona Live London 2014. (Note that pricing of Google Cloud SQL changed prices on the same day after the presentation)
MariaDB Server 10.3 is a culmination of features from MariaDB Server 10.2+10.1+10.0+5.5+5.3+5.2+5.1 as well as a base branch from MySQL 5.5 and backports from MySQL 5.6/5.7. It has many new features, like a GA-ready sharding engine (SPIDER), MyRocks, as well as some Oracle compatibility, system versioned tables and a whole lot more.
Presented at OSCON 2018. A review of what is available from MySQL, MariaDB Server, MongoDB, PostgreSQL, and more. Covering your choices, considerations, versions, access methods, cost, a deeper look at RDS and if you should run your own instances or not.
MySQL features missing in MariaDB ServerColin Charles
MySQL features missing in MariaDB Server. Here's an overview from the New York developer's Unconference in February 2018. This is primarily aimed at the developers, to decide what goes into MariaDB 10.4, as opposed to users.
High level comparisons are made between MySQL 5.6/5.7 with of course MySQL 8.0 as well. Here's to ensuring MariaDB Server 10/310.4 has more "Drop-in" compatibility.
With a focus on Amazon AWS RDS MySQL and PostgreSQL, Rackspace cloud, Google Cloud SQL, Microsoft Azure for MySQL and PostgreSQL as well as a hint of the other clouds
Percona ServerをMySQL 5.6と5.7用に作るエンジニアリング(そしてMongoDBのヒント)Colin Charles
Engineering that goes into making Percona Server for MySQL 5.6 & 5.7 different (and a hint of MongoDB) for dbtechshowcase 2017 - the slides also have some Japanese in it. This should help a Japanese audience to read it. If there are questions due to poor translation, do not hesitate to drop me an email (byte@bytebot.net) or tweet: @bytebot
Databases require capacity planning (and to those coming from traditional RDBMS solutions, this can be thought of as a sizing guide). Capacity planning prevents resource exhaustion. Capacity planning can be hard. This talk has a heavier leaning on MySQL, but the concepts and addendum will help with any other data store.
Tuning Linux for your database FLOSSUK 2016Colin Charles
Some best practices about tuning Linux for your database workloads. The focus is not just on MySQL or MariaDB Server but also on understanding the OS from hardware/cloud, I/O, filesystems, memory, CPU, network, and resources.
Having spent more than the last decade being the main point of contact for distributions shipping MySQL, then MariaDB Server, it's clear that working with distributions have many challenges. Licensing changes (when MySQL moved the client libraries from LGPL to GPL with a FOSS Exception), ABI changes, speed (or lack thereof) of distribution releases/freezes, supporting the software throughout the lifespan of the distribution, specific bugs due to platforms, and a lot more will be discussed in this talk. Let's not forget the politics. How do we decide "tiers" of importance for distributions? As a bonus, there will be a focus on how much effort it took to "replace" MySQL with MariaDB.
Benefits: if you're making a distribution, this is the point of view of the upstream package makers. Why are distribution statistics important to us? Do we monitor your bugs system or do you have a better escalation to us? How do we test to make sure things are going well before release. This and more will be spoken about.
As an upstream project (package), we love nothing more than being available everywhere. But time and energy goes into making this is so as there are quirks in every distribution.
Do you wonder how to contribute to MariaDB? Have you considered writing a plugin? MariaDB ships many plugins (over a hundred) and you could also be one of them. Find out what they do, how to use them, and so forth. A lightning talk given for the MySQL NL User Group meetup in Amsterdam.
Better encryption & security with MariaDB 10.1 & MySQL 5.7Colin Charles
Talking about the improvements in MariaDB on MySQL security and encryption features that are so important in today's data landscape. Presented http://www.meetup.com/EffectiveMySQL/events/224828891/
Le nuove frontiere dell'AI nell'RPA con UiPath Autopilot™UiPathCommunity
In questo evento online gratuito, organizzato dalla Community Italiana di UiPath, potrai esplorare le nuove funzionalità di Autopilot, il tool che integra l'Intelligenza Artificiale nei processi di sviluppo e utilizzo delle Automazioni.
📕 Vedremo insieme alcuni esempi dell'utilizzo di Autopilot in diversi tool della Suite UiPath:
Autopilot per Studio Web
Autopilot per Studio
Autopilot per Apps
Clipboard AI
GenAI applicata alla Document Understanding
👨🏫👨💻 Speakers:
Stefano Negro, UiPath MVPx3, RPA Tech Lead @ BSP Consultant
Flavio Martinelli, UiPath MVP 2023, Technical Account Manager @UiPath
Andrei Tasca, RPA Solutions Team Lead @NTT Data
Epistemic Interaction - tuning interfaces to provide information for AI supportAlan Dix
Paper presented at SYNERGY workshop at AVI 2024, Genoa, Italy. 3rd June 2024
https://alandix.com/academic/papers/synergy2024-epistemic/
As machine learning integrates deeper into human-computer interactions, the concept of epistemic interaction emerges, aiming to refine these interactions to enhance system adaptability. This approach encourages minor, intentional adjustments in user behaviour to enrich the data available for system learning. This paper introduces epistemic interaction within the context of human-system communication, illustrating how deliberate interaction design can improve system understanding and adaptation. Through concrete examples, we demonstrate the potential of epistemic interaction to significantly advance human-computer interaction by leveraging intuitive human communication strategies to inform system design and functionality, offering a novel pathway for enriching user-system engagements.
Accelerate your Kubernetes clusters with Varnish CachingThijs Feryn
A presentation about the usage and availability of Varnish on Kubernetes. This talk explores the capabilities of Varnish caching and shows how to use the Varnish Helm chart to deploy it to Kubernetes.
This presentation was delivered at K8SUG Singapore. See https://feryn.eu/presentations/accelerate-your-kubernetes-clusters-with-varnish-caching-k8sug-singapore-28-2024 for more details.
Essentials of Automations: The Art of Triggers and Actions in FMESafe Software
In this second installment of our Essentials of Automations webinar series, we’ll explore the landscape of triggers and actions, guiding you through the nuances of authoring and adapting workspaces for seamless automations. Gain an understanding of the full spectrum of triggers and actions available in FME, empowering you to enhance your workspaces for efficient automation.
We’ll kick things off by showcasing the most commonly used event-based triggers, introducing you to various automation workflows like manual triggers, schedules, directory watchers, and more. Plus, see how these elements play out in real scenarios.
Whether you’re tweaking your current setup or building from the ground up, this session will arm you with the tools and insights needed to transform your FME usage into a powerhouse of productivity. Join us to discover effective strategies that simplify complex processes, enhancing your productivity and transforming your data management practices with FME. Let’s turn complexity into clarity and make your workspaces work wonders!
Why You Should Replace Windows 11 with Nitrux Linux 3.5.0 for enhanced perfor...SOFTTECHHUB
The choice of an operating system plays a pivotal role in shaping our computing experience. For decades, Microsoft's Windows has dominated the market, offering a familiar and widely adopted platform for personal and professional use. However, as technological advancements continue to push the boundaries of innovation, alternative operating systems have emerged, challenging the status quo and offering users a fresh perspective on computing.
One such alternative that has garnered significant attention and acclaim is Nitrux Linux 3.5.0, a sleek, powerful, and user-friendly Linux distribution that promises to redefine the way we interact with our devices. With its focus on performance, security, and customization, Nitrux Linux presents a compelling case for those seeking to break free from the constraints of proprietary software and embrace the freedom and flexibility of open-source computing.
PHP Frameworks: I want to break free (IPC Berlin 2024)Ralf Eggert
In this presentation, we examine the challenges and limitations of relying too heavily on PHP frameworks in web development. We discuss the history of PHP and its frameworks to understand how this dependence has evolved. The focus will be on providing concrete tips and strategies to reduce reliance on these frameworks, based on real-world examples and practical considerations. The goal is to equip developers with the skills and knowledge to create more flexible and future-proof web applications. We'll explore the importance of maintaining autonomy in a rapidly changing tech landscape and how to make informed decisions in PHP development.
This talk is aimed at encouraging a more independent approach to using PHP frameworks, moving towards a more flexible and future-proof approach to PHP development.
SAP Sapphire 2024 - ASUG301 building better apps with SAP Fiori.pdfPeter Spielvogel
Building better applications for business users with SAP Fiori.
• What is SAP Fiori and why it matters to you
• How a better user experience drives measurable business benefits
• How to get started with SAP Fiori today
• How SAP Fiori elements accelerates application development
• How SAP Build Code includes SAP Fiori tools and other generative artificial intelligence capabilities
• How SAP Fiori paves the way for using AI in SAP apps
GraphRAG is All You need? LLM & Knowledge GraphGuy Korland
Guy Korland, CEO and Co-founder of FalkorDB, will review two articles on the integration of language models with knowledge graphs.
1. Unifying Large Language Models and Knowledge Graphs: A Roadmap.
https://arxiv.org/abs/2306.08302
2. Microsoft Research's GraphRAG paper and a review paper on various uses of knowledge graphs:
https://www.microsoft.com/en-us/research/blog/graphrag-unlocking-llm-discovery-on-narrative-private-data/
The Metaverse and AI: how can decision-makers harness the Metaverse for their...Jen Stirrup
The Metaverse is popularized in science fiction, and now it is becoming closer to being a part of our daily lives through the use of social media and shopping companies. How can businesses survive in a world where Artificial Intelligence is becoming the present as well as the future of technology, and how does the Metaverse fit into business strategy when futurist ideas are developing into reality at accelerated rates? How do we do this when our data isn't up to scratch? How can we move towards success with our data so we are set up for the Metaverse when it arrives?
How can you help your company evolve, adapt, and succeed using Artificial Intelligence and the Metaverse to stay ahead of the competition? What are the potential issues, complications, and benefits that these technologies could bring to us and our organizations? In this session, Jen Stirrup will explain how to start thinking about these technologies as an organisation.
A tale of scale & speed: How the US Navy is enabling software delivery from l...sonjaschweigert1
Rapid and secure feature delivery is a goal across every application team and every branch of the DoD. The Navy’s DevSecOps platform, Party Barge, has achieved:
- Reduction in onboarding time from 5 weeks to 1 day
- Improved developer experience and productivity through actionable findings and reduction of false positives
- Maintenance of superior security standards and inherent policy enforcement with Authorization to Operate (ATO)
Development teams can ship efficiently and ensure applications are cyber ready for Navy Authorizing Officials (AOs). In this webinar, Sigma Defense and Anchore will give attendees a look behind the scenes and demo secure pipeline automation and security artifacts that speed up application ATO and time to production.
We will cover:
- How to remove silos in DevSecOps
- How to build efficient development pipeline roles and component templates
- How to deliver security artifacts that matter for ATO’s (SBOMs, vulnerability reports, and policy evidence)
- How to streamline operations with automated policy checks on container images
Generative AI Deep Dive: Advancing from Proof of Concept to ProductionAggregage
Join Maher Hanafi, VP of Engineering at Betterworks, in this new session where he'll share a practical framework to transform Gen AI prototypes into impactful products! He'll delve into the complexities of data collection and management, model selection and optimization, and ensuring security, scalability, and responsible use.
Smart TV Buyer Insights Survey 2024 by 91mobiles.pdf91mobiles
91mobiles recently conducted a Smart TV Buyer Insights Survey in which we asked over 3,000 respondents about the TV they own, aspects they look at on a new TV, and their TV buying preferences.
Smart TV Buyer Insights Survey 2024 by 91mobiles.pdf
The Complete MariaDB Server tutorial
1. The Complete MariaDB Server Tutorial
Colin Charles, Chief Evangelist, Percona Inc.
colin.charles@percona.com / byte@bytebot.net
http://www.bytebot.net/blog/ | @bytebot on Twitter
Percona Live Europe Amsterdam, Netherlands
3 October 2016
3. whoami
• Chief Evangelist (in the CTO office), Percona Inc
• Founding team of MariaDB Server (2009-2016),
previously at Monty Program Ab, merged with
SkySQL Ab, now MariaDB Corporation
• Formerly MySQL AB (exit: Sun Microsystems)
• Past lives include Fedora Project (FESCO),
OpenOffice.org
• MySQL Community Contributor of theYear Award
winner 2014
3
4. MariaDB is very social
• facebook: fb.com/MariaDB.dbms
• twitter: @MariaDB
• g+: plus.google.com/+mariadb/
• Tweet things you learn with #mariadb
4
5. Agenda
• This talk is about MariaDB Server from the
MariaDB Foundation
• There is no focus on MariaDB MaxScale or
MariaDB ColumnStore from the MariaDB
Corporation
5
10. What is MariaDB?
10
• Community developed
• Feature enhanced
• MariaDB doesn’t depend on MySQL for development -
many features are developed independently of MySQL
• Backwards compatible with MySQL
• (kind of) feature complete
• replication supported for easy migration
11. Aims of MariaDB
• Compatible, drop-in replacement to MySQL
• your application shouldn’t care that its
running MariaDB, easy upgrade (uninstall
mysql, install mariadb, continue ops!)
• Stable (bug-free) releases with no
regressions
• GPLv2
11
12. 6 years, many server
releases
• MariaDB 5.1, GA February 2010
• MariaDB 5.2, GA November 2010
• MariaDB 5.3, GA February 2012
• MariaDB 5.5, GA April 2012
• MariaDB Galera Cluster, GA March 2013
• MariaDB 10.0.10 (March 2014)
• MariaDB 10.1.8 (October 2015)
12
14. MariaDB 5.6?
• There will never be a MariaDB 5.6 - the
numbers have changed
• Many companies will still continue to
support both MySQL and MariaDB releases
14
17. Importance of understanding
MariaDB (and MySQL)
• Generics are inefficient
• Since you have chosen MariaDB:
• maximise its strengths
• minimise its weaknesses
17
18. Sample databases to
play with
• http://dev.mysql.com/doc/index-other.html
• sakila sample database, world
database (used in MySQL training),
menagerie database (used in book:
Beginning MySQL), employees
database (large dataset, comes with data -
best to play with)
18
19. Picking hardware
• Just use 64-bit hardware
• VM’s are improving to use 64-bit OSes &
software
• Physical > virtual
• Disk: battery backed storage, plan for RAID
usage
• MariaDB 10.1 has optimisations for flash/SSD/
FusionIO
19
20. Testing MySQL
• Use MySQL Sandbox
• http://mysqlsandbox.net/
• Express one-click MySQL installs
• make_sandbox foo.tar.gz
• Does not require root privileges
20
21. Installation
• Binaries (tarballs) are available at http://mariadb.org/ (source too)
• Built, tested by MariaDB
• Graphical installer & configuration for Microsoft Windows, with
HeidiSQL GUI
• Up-to-date predictable release schedule
• RPM, DEB packages are provided, includingYUM & APT
repositories
• Use the repository configuration tool
• Inside Linux/*BSD distributions
• Easy to install, basic defaults, may be older than upstream
21
22. Upgrades
• Review changelogs carefully, even for minor
versions
• Make backups (using xtrabackup)
• Don’t forget to run mysql_upgrade
• by default with a distribution package
• Replication can reduce downtime by upgrading
the slave, promoting it, then upgrading the master
22
23. Upgrading from MySQL
5.0
• MariaDB 5.1 fixes upgrades better than MySQL 5.1
handles this
• InnoDB + Archive tables upgraded properly
• mysql_upgrade, mysqlcheck have more options to see
what’s going on
• mysqlcheck wrong warnings removed
• MySQL 5.1 -> MariaDB 5.1 is “drop-in”
• https://mariadb.com/kb/en/upgrading-to-mariadb-from-
mysql/
23
24. Packages (RPM
example)
• MariaDB-common
• character sets
• MariaDB-shared
• latest libmysqlclient, some plugins,
/etc/my.cnf.d/
• MariaDB-compat
• compatible client libraries that
replace mysql-libs
• MariaDB-server
• The actual server!
• MariaDB-client
• mysql client utilities
• MariaDB-test
• test suite
• MariaDB-devel
• development headers enabling
you to build your own package
• MariaDB-CassandraSE
• plugin for CassandraSE
24
25. What is libmysqlclient?
• Client libraries
• Many applications are compiled against
libmysqlclient
• It is an Application Binary Interface (ABI)
• When you write in Java & use Connector/J,
Connector/J is compiled against libmysqlclient
• Similarly with PHP & Connector/PHP
25
26. MySQL utilities
• Why does MariaDB use all the same client utilities?
• Because the aim is to be a compatible drop-in
replacement
• There are very few non-MySQL utilities shipped:
aria_chk, aria_dump_log, aria_ftdump,
aria_pack, aria_read_log
• xtstat (PBXT) is deprecated in MariaDB 5.5
onwards
• mytop as it adds features not-present upstream
26
27. Finding help
• How do you know what CLI options to use?
• Use the man(ual) pages!
•man mysql
• man <command_name> usually works for
any CLI command
• HELP SELECT in mysql works too (help
tables) - HELP <operator>
27
28. Error messages
• perror is a great tool
• MariaDB-specific errors are 1900 and
above
• https://mariadb.com/kb/en/mariadb-error-
codes/#mariadb-specific-error-codes
28
29. mysql_secure_insta
llation
• Now that you’ve tested MySQL works fine (by
default, no root password), it’s time to ensure you
secure the installation
• Set root password
• Remove anonymous users
• Disallow remote root login
• Remove test database
• Reload privileges
29
30. mysqladmin
• Manage user accounts, passwords,
permissions
• Display mysqld settings & status counters
• Shutdown, create, drop databases
shell> mysqladmin processlist
shell> mysqladmin extended-status
shell> mysqladmin -uroot -p create wordpress
30
SHOW PROCESSLIST
SHOW STATUS
31. mysqldump
• Dump schema and/or data to .sql file, tab
• Useful for backups, transferring data
• Locks for consistency, so troublesome
shell> mysqldump --all-databases > backup.sql
shell> mysqldump --all-databases --single-transaction >
backup.sql
31
32. Other tools
• There are many other command line
tools...
• Front-ends
• HeidiSQL
• Webyog’s SQLyog
• Sequel Pro (OSX)
32
34. Making client
connections
• TCP/IP is available on all platforms
• disable using --skip-networking
• Socket files available on Unix
• fastest communication path
• MySQL connections are generally cheap
• If you have many short running queries (typical web
app), you benefit from MariaDB threadpool
• Set connection limit max_connections=n in my.cnf
34
35. Connection Pool
• mysqld’s main thread listens for connections
• Each connection has a thread assigned to it
• Threads can be:
• created newly
• reused from thread cache
• User authentication processed based on hostname,
username & password
• Client specific buffers for session variables are allocated
35
37. Query Cache
• Stores SELECT queries and their result sets
• Subquery cache exists only in MariaDB
• Frequently changed table data will cause
queries to naturally be missed
• Regularly replaced these days with
memcached, et al.
37
38. SQL Parser
• Lexical scanner & grammar rules
• Parse SQL into tokens
• Apply grammar rules to check statement
validity
• Construct a parse tree for Optimizer to
use
38
39. Optimizer
• Reads the parse tree and calculates the best query
execution plan (QEP) to handle query
• find indexes
• determine JOIN order
• eliminate unnecessary tables
• etc.
• The optimizer is smart, don’t try to force query
plans
39
40. Pluggable Storage
Engines
• MariaDB can use many storage engines
with different features
• Installed/removed on fly with INSTALL/
UNINSTALL PLUGIN
• Mixing & matching on same server, even on
same query
40
41. Value proposition
• Unmatched flexibility + customisation potential
• MEMORY engine for performance/routine
lookup data
• Right storage engine can improve performance
in many applications
• ARCHIVE compresses data, up to 80%
• Partners & community benefit from this
41
42. What makes engines
different?
• Storage: how the data is stored on disk
• Or in NDB (memory+disk), CassandraSE (access a Cassandra Cluster), SphinxSE
(access the Sphinx daemon)
• Indexes: improves search operations
• Memory usage: improves data access for speed
• Transactions: protects the integrity of your data (Atomic-Consistent-Isolated-
Durable - ACID)
• Locking level: MyISAM (table locks), InnoDB (row locks), old BDB (page locks)
• Data types: Data types may be converted, MEMORY doesn’t support TEXT, etc.
• Caching: InnoDB caches data & indexes, MyISAM caches indexes only (relying on OS
disk cache for data)
• Full-text search capability: MyISAM has this, InnoDB 5.6 got this
• GIS: MyISAM & Aria work (R-tree indexes exist), InnoDB 5.7 has this too
42
43. INFORMATION_SCHE
MA
• Holds metadata (data about the data) on all
other databases & tables, exposed as
regular tables
• Generated on the fly
• Has extensions in MariaDB as we expose
more data than native MySQL
43
44. PERFORMANCE_SCH
EMA
• Allows for monitoring execution at a low
level
• This is a storage engine, monitoring server
events (anything that takes time & can be
instrumented)
• Tables are views or temporary tables that
use no on-disk storage
44
45. Transactional vs. non-
transactional
• Transaction-safe tables
(InnoDB) have advantages
over non-transaction safe
tables (MyISAM):
• server crash? Automatic
recovery, or a backup
+transaction log
• ROLLBACK can be
executed to ignore
changes
• Update fails? Changes
reverted
• Concurrency - tables w/
many update +
concurrent reads
• Disadvantages in today’s
environments (transaction
overhead = slower), more
disk space requirements,
more memory to perform
updates don’t seem like they
apply any longer
45
46. Indexes
• Tree Indexes
• B-Trees
• B+Trees (InnoDB)
• T-Trees (NDB)
• Red-black binary trees
(MEMORY)
• R-Trees (MyISAM for spatial
indexes)
• Hash Indexes (MEMORY, NDB,
InnoDB)
• If table fits entirely in
memory, fastest way to
perform queries is a hash
index
• InnoDB has an internal
adaptive hash index. InnoDB
monitors index searches,
and if it notices that it will
benefit from a hash index,
InnoDB automatically builds
one. (5.1.24 and greater)
46
47. MyISAM
• Pros?
• excellent INSERT
performance
• small footprint
• supports full-text
search (FTS)
• Cons?
• no transactions
• no foreign key
support
• Typical uses
• logging
• auditing
• data warehousing
47
48. MyISAM II
• In my.cnf, remember to
set the key_buffer_size.
This is memory*0.40, as
MyISAM uses the OS
cache for tables
• myisam_use_mmap
enables MyISAM to use
memory mapping
(7-40% speed
improvement)
• key_cache_segments =
1 enables segmented key
caches in MariaDB -
~250% improvements, as
it mitigates thread
contention for key cache
lock
48
49. MyISAM segmented key
caches
• Mitigates thread contention for key cache lock, with
notable performance improvements
• Key caches divided into different segments, allowing
for better key cache concurrency
• 1-64 segments
49
50. InnoDB
• Maintains its own buffer pool (does
aggressive memory caching)
• Uses tablespaces (several files on disk, raw
disk support)
• Typically used for OLTP operations
50
51. ARCHIVE
• Store large amounts of data without
indexes, in small disk footprint
• SELECT and INSERT operations only
• Good for data audit use
• Uses AZIO (zlib) compression
51
52. FederatedX
• Create logical pointers to tables that exist on other MySQL servers;
these can then be linked together to form one logical database
• A federated table pointing to an InnoDB table on another server, will
have transaction support (in 5.1)
• Capabilities limited to underlying engine on remote server
• CREATE TABLE t1 (...) ENGINE=FEDERATED
CONNECTION='mysql://username:pwd@myhost:3306/db_name/
tbl_name
• Can also be used for synchronous replication
• Federated table on master server pointing to slave; triggers on
master table to write all changes to remote table once applied to
the master
52
53. Memory
• Previously known as HEAP tables
• In-memory engine
• Hash index used by default (changes in 5.2,
enable much better INSERT performance),
B-Tree available too
• https://mariadb.com/kb/en/performance-of-
memory-tables/
53
54. Aria
• Based off the 5.1 code
• 1.0 – crash-safe MyISAM, with cacheable row format
• 1.5 – concurrent INSERT/SELECT
• Soon to be merged into 6.0, then...
• 2.0: transactional + ACID compliance
• 3.0: high concurrency, online backup
• Goal:ACID compliant, MVCC transactional storage engine, based on MyISAM
• Target? Data warehousing
• Uses big log files (1GB by default)
• 8K pages used by default (MyISAM uses 1K pages)
• Has group commit (MariaDB 5.2) to speed up inserts
54
55. PBXT (deprecated)
• MVCC, transactional,ACID compliant, foreign key
support
• row-level locking for updates, so maximum concurrency
• immediate notification if client processes are
deadlocked
• write-once, as it uses a log-based architecture (write
data to DB without first writing to transaction log)
• support for BLOB streaming with Blob Streaming
engine
55
56. Storage Engine API
• http://dev.mysql.com/tech-resources/
articles/creating-new-storage-engine.html
• SHOW PLUGINS;
• https://kb.askmonty.org/v/extending-create-
table
• storage/example/ha_example.cc and
storage/example/ha_example.h
56
57. Writing your own
• Find the plugin path - show variables like “%plugin%”;
+-----------------+-----------------------------------------------+
| Variable_name | Value |
+-----------------+-----------------------------------------------+
| plugin_dir | /usr/local/Cellar/mariadb/10.0.15/lib/plugin/ |
| plugin_maturity | unknown |
+-----------------+-----------------------------------------------+
• note that this is also where you store UDFs
• Copy the relevant engine (eg. myengine.so)
• INSTALL PLUGIN myengine SONAME 'myengine.so';
• Server registers plugin to mysql.plugin table, and now ENGINE=myengine will work
57
58. Things to think about
• Backup is not engine-independent
• MyISAM, InnoDB,TokuDB
• LVM/ZFS snapshots mitigate this
• Different engines have different monitoring
options
• Mix and match; use summary tables
58
59. Survey of popular OSS
tools - what they use
• Wordpress (blog): uses default engine, MyISAM is fine
• MediaWiki (wiki): prefers InnoDB, except for
“searchindex” table, which is MyISAM
• http://svn.wikimedia.org/viewvc/mediawiki/trunk/
phase3/maintenance/tables.sql?view=markup
• vBulletin (forum): MyISAM
• SugarCRM (CRM): MyISAM (with conversion script to
InnoDB provided)
• Zimbra Collaboration Suite: InnoDB
59
61. We start with...
• What came in 5.1, 5.2, 5.3, 5.5 (jump
around appropriately)
• What comes in 10.0 series
• I won’t talk about deprecated features like
PBXT in-depth, or even the old MariaDB
5.1 pool of threads (5.5 threadpool is
better + improvements in 10.1)
61
62. XtraDB
• A more performant
InnoDB designed to
scale on modern
hardware
• Less checkpointing
(smoother), less flushing
to disk
62
63. InnoDB notes
• SHOW GLOBALVARIABLES LIKE ‘innodb_ver
%';
• Important - ship XtraDB and merge with
different Percona Server versions
• eg. innodb_adaptive_flushing_method - native|
estimate|keep_average - where was reflex?
• (okay, 5.6 compatibility,
innodb_adaptive_flushing eventually)
63
64. InnoDB Fake Changes
• InnoDB Fake Changes for replication pre-
fetching (for DML operations)
• Great for buffer pool warmup
• Consider using multi-threaded slaves in 10.2
• https://www.percona.com/doc/percona-
server/5.6/management/
innodb_fake_changes.html
64
65. Log archiving
• Log archiving (use to create incremental
backups with xtrabackup)
• When log archiving is enabled, it duplicates
all redo log writes in a separate set of files
in addition to normal redo log writing,
creating new files as necessary.
• https://www.percona.com/doc/percona-
server/5.6/management/log_archiving.html
65
66. SHOW ENGINE
INNODB STATUS
• Extended, reorganised
• Information about internal hash tables
Internal hash tables (constant factor + variable
factor)
Adaptive hash index 2446944 (2213368 + 233576)
Page hash 139112 (buffer pool 0 only)
Dictionary cache 788235 (554768 + 233467)
File system 829168 (812272 + 16896)
Lock system 333592 (332872 + 720)
Recovery system 0 (0 + 0)
66
67. Count InnoDB
deadlocks
• Show deadlocks since the server has
started
• SHOW GLOBAL STATUS LIKE
‘innodb_deadlocks';
• + SHOW ENGINE INNODB MUTEX;
67
69. Switching between
XtraDB & InnoDB
mysqld --ignore-builtin-innodb --plugin-
load=innodb=ha_innodb.so --plugin_dir=/usr/local/
mysql/lib/mysql/plugin
Or in my.cnf
[mysqld]
ignore-builtin-innodb
plugin-load=innodb=ha_innodb.so
plugin_dir=/usr/local/mysql/lib/mysql/plugin
69
70. Usernames
• Usernames in MariaDB > 5.5.31? 80 character limit (which
you have to reload manually)
create user
'long12345678901234567890'@'localhost'
identified by 'pass';
Query OK, 0 rows affected (0.01 sec)
vs
ERROR 1470 (HY000): String
'long12345678901234567890' is too long for
user name (should be no longer than 16)
70
71. MariaDB 5.5: an
opensource threadpool
• Modified from 5.1 (libevent
based), great for CPU
bound loads and short
running queries
• No minimization of
concurrent transactions
with dynamic pool size
• thread_handling=po
ol-of-threads
• https://mariadb.com/kb/en/
mariadb/thread-pool-in-
mariadb/
71
72. Improved threadpool
• You can limit resources used by threads:
thread_pool_max_threads
• SHOW GLOBALVARIABLES LIKE
'%thread_%';
72
73. Better for DBAs: async
client library
• start operation, do work
in thread, operation
processed, result travels
back
• use cases: multiple
queries against single
server (utilize more
CPUs); queries against
multiple servers
(SHOW STATUS on
many machines)
• https://
kb.askmonty.org/en/
about-non-blocking-
operation-in-the-
client-library/
• fast node.js driver
available: mariasql
• https://
kb.askmonty.org/en/
mariasql-for-nodejs/
73
74. LIMIT ROWS
EXAMINED
• The purpose of this
optimization is to
provide the means to
terminate the execution
of SELECT statements
which examine too
many rows, and thus use
too many resources.
•SELECT * from
t1, t2 LIMIT 10
ROWS EXAMINED
1000;
• https://kb.askmonty.org/
en/limit-rows-examined/
74
75. SHOW STATUS
• SHOW STATUS provides server status
information. It is like mysqladmin extended-status.
•SHOW STATUS LIKE ‘Key%’;
• https://kb.askmonty.org/en/show-status/
• https://kb.askmonty.org/en/server-status-variables/
• MariaDB has opened_views, executed_triggers,
executed_events, feature_* as new options
75
76. SQL Error Logging
Plugin
• Log errors sent to clients in a log file that
can be analysed later. Log file can be rotated
(recommended)
• a MYSQL_AUDIT_PLUGIN
install plugin SQL_ERROR_LOG
soname 'sql_errlog.so';
76
77. Audit Plugin
• Log server activity - who connects to the
server, what queries run, what tables touched -
rotating log file or syslogd
• MariaDB has extended the audit API, so user
filtering is possible
• a MYSQL_AUDIT_PLUGIN
INSTALL PLUGIN server_audit SONAME
‘server_audit.so’;
77
78. Replication: selective
skipping
• All changes that are logged as events in the
binlog are replicated to all slaves
• However, sometimes you want all to be logged
to binlog but skipped replication to slaves
• @@skip_replication (session only)
• replicate_events_marked_for_skip
= replicate|filter_on_slave|
filter_on_master (dynamic)
78
79. Replication: dynamic
variables
• The variables replicate_do_*,
replicate_ignore_*, and replicate_wild_*
have been made dynamic, so they can be
changed without requiring a server restart.
• https://kb.askmonty.org/en/dynamic-
replication-variables/
79
80. Replication:Annotation
of RBR events
• MariaDB supports statement & row based
replication (RBR)
• In RBR, the binlog has no SQL statements,
only events are logged (INSERT, DELETE, etc)
• Option to include original SQL statement
(default OFF)
• https://kb.askmonty.org/en/
annotate_rows_log_event/
80
81. Replication: binlog
event checksums
• Backport from MySQL 5.6 (in MariaDB
5.3+)
• binlog_checksum option
• Slaves perform checksums on events
received & will stop if there is corruption
• https://kb.askmonty.org/en/binlog-event-
checksums/
81
82. Replication: group
commit in the binary log
•sync_binlog=1,
innodb_flush_log_at_trx_commit
=1
• https://www.facebook.com/note.php?
note_id=10150261692455933
• http://kb.askmonty.org/en/group-commit-for-
the-binary-log
• SHOW STATUS LIKE 'binlog_%commits';
82
83. Group commit in
MariaDB 5.3 onwards
• Do slow part of prepare() in parallel in
InnoDB (first fsync(), InnoDB group
commit)
• Put transaction in queue, decide commit
order
83
84. • First in queue runs serial part for all, rest
wait
• Wait for access to the binlog
• Write transactions into binlog, in order,
then sync (second fsync())
• Run the fast part of commit() for all
transactions in order
84
85. • Finally, run the slow part of commit() in
parallel (third fsync(), InnoDB group
commit)
• Only 2 context switches per thread (one
sleep, one wakeup)
• Note: MySQL 5.6, MariaDB 10 only does 2
fsyncs/group commit
85
86. Group commit in
MariaDB 10
• Remove commit in slow part of InnoDB
commit (stage 4)
• Reduce cost of crash-safe binlog
• A binlog checkpoint is a point in the
binlog where no crash recovery is
needed before it. In InnoDB you wait for
flush + fsync its redo log for commit
86
87. crash-safe binlog
• MariaDB 5.5 checkpoints after every
commit —> quite expensive!
• 5.5/5.6 stalls commits around binlog rotate,
waiting for all prepared transactions to
commit (since crash recovery can only scan
latest binlog file)
87
88. crash-safe binlog 10.0
• 10.0 makes binlog checkpoints
asynchronous
• A binlog can have no checkpoints at all
• Ability to scan multiple binlogs during
crash recovery
• Remove stalls around binlog rotates
88
89. Extensions to the SE
API
• prepare() - write prepared trx in
parallel w/group commit
• prepare_ordered() - called serially, in
commit order
• commit_ordered() - called serially, in
commit order; fast commit to memory
• commit() - commit to disk in parallel,
89
90. group commit in 10.1
• Tricky locking issues hard to change without getting deadlocks
sometimes
• mysql#68251, mysql#68569
• New code? Binlog rotate in background thread (further reducing
stalls). Split transactions across binlogs, so big transactions do not
lead to big binlog files
• Enhanced semi-sync replication (wait for slave before commit on
the master rather than after commit)
90
91. Replication: START TRANSACTION
WITH CONSISTENT SNAPSHOT
• Works with the binlog, possible to obtain the binlog position
corresponding to a transactional snapshot of the database without
blocking any other queries.
• by-product of group commit in the binlog to view commit
ordering
• Used by the command mysqldump--single-transaction
--master-data to do a fully non-blocking backup
• Works consistently between transactions involving more than one
storage engine
• https://kb.askmonty.org/en/enhancements-for-start-transaction-
with-consistent/
91
92. GIS support!
• MySQL has OpenGIS SFS (Simple feature access,
SQL access method)
• Now, SQL with full geometry types
• ST_ prefix (incl. ST_RELATE,
ST_BOUNDARY, etc.)
• MyISAM,Aria for SPATIAL & non-spatial indexes
• When 5.7-InnoDB is merged, it will get
support too
92
93. GIS II
• Spatial reference systems support
(REF_SYSTEM_ID) can be specified as a column
attribute
• INFORMATION_SCHEMA.GEOMETRY_COLUMN
S for queries of references
• Use Osmosis, you can load all OpenStreetMap data
into MariaDB now
• https://mariadb.com/kb/en/gis-features-in-533/
• https://mariadb.com/kb/en/openstreetmap-dataset/
93
94. Progress reporting
• ALTER TABLE & LOAD DATA INFILE
MariaDB [mail]> alter table mail engine = maria;
Stage: 1 of 2 'copy to tmp table' 17.55% of stage done
MariaDB [mail]> select id, user, db, command, state,
-> time_ms, progress from information_schema.processlist;
+---------+-------------------+-----------+----------+
| command | state | time_ms | progress |
+---------+-------------------+-----------+----------+
| Query | copy to tmp table | 23407.131 | 17.551 |
+---------+-------------------+-----------+----------+
1 row in set (0.47 sec)
94
95. TIME_MS in
I_S.PROCESSLIST
• Extra column 'TIME_MS' has been added to
the
INFORMATION_SCHEMA.PROCESSLIST
table
• Units of milliseconds with microsecond
precision (the unit and precision of the
'TIME' column is one second).
95
96. 5.7 I_S.PROCESSLIST
+---------+---------------------+------+-----+---------+-------+
| Field | Type | Null | Key | Default | Extra |
+---------+---------------------+------+-----+---------+-------+
| ID | bigint(21) unsigned | NO | | 0 | |
| USER | varchar(32) | NO | | | |
| HOST | varchar(64) | NO | | | |
| DB | varchar(64) | YES | | NULL | |
| COMMAND | varchar(16) | NO | | | |
| TIME | int(7) | NO | | 0 | |
| STATE | varchar(64) | YES | | NULL | |
| INFO | longtext | YES | | NULL | |
+---------+---------------------+------+-----+---------+-------+
8 rows in set (0.00 sec)
96
98. New KILL syntax
• HARD | SOFT & USER USERNAME are MariaDB-specific
(5.3.2)
• KILL QUERY ID query_id (10.0.5) - kill by query id, rather
than thread id
• SOFT ensures things that may leave a table in an inconsistent
state aren’t interrupted (like REPAIR or INDEX creation for
MyISAM or Aria)
KILL [HARD | SOFT] [CONNECTION | QUERY]
[thread_id | USER user_name]
98
99. Statistics
• Understand server activity better to understand database loads
•SET GLOBAL userstat=1;
•SHOW CLIENT_STATISTICS; SHOW USER_STATISTICS;
• # of connections, CPU usage, bytes received/sent, row statistics
•SHOW INDEX_STATISTICS; SHOW TABLE_STATISTICS;
• # rows read, changed, indexes
• INFORMATION_SCHEMA.PROCESSLIST has MEMORY_USAGE,
EXAMINED_ROWS (similar with SHOW STATUS output)
99
MariaDB 10.0+
101. The old days
• Download MySQL, including sources
• Download SphinxSE for compiling
• Download Sphinx to compile with MySQL
support
• Documented: http://www.howtoforge.com/
sphinx-as-mysql-storage-engine-sphinxse
101
102. Today
• Install sphinx from your distribution
• Install MariaDB 5.5 from your distribution
or from http://mariadb.org/
• Get started!
102
105. What is SphinxSE?
• SphinxSE is just the storage engine that still
depends on the Sphinx daemon
• It doesn’t store any data itself
• Its just a built-in client to allow MariaDB to
talk to Sphinx searchd, run queries, obtain
results
• Indexing, searching is performed on Sphinx
105
106. Configure sphinx!
• /usr/local/sphinx/sphinx.conf
• Source (multiple, include mysql, with
connection info)
• Setup indexer (esp. if its on localhost) -
mem_limit, max_iops, max_iosize
• Setup searchd (where to listen to, query
log, etc.)
106
107. Use case scenarios
• Already have an existing application that
makes use of full-text-search in MyISAM?
Porting should be easier
• Have a programming language without a
native API for Sphinx? Surely there’s a
connector for MariaDB ;-)
107
108. Use case scenarios
• Results from Sphinx itself almost always
require additional work involving MariaDB
• Say to pull out text column that Sphinx
index doesn’t store
• JOIN with another table (using a different
engine)
108
109. An example
CREATE TABLE t1
(
id INTEGER UNSIGNED NOT NULL,
weight INTEGER NOT NULL,
query VARCHAR(3072) NOT NULL,
group_id INTEGER,
INDEX(query)
) ENGINE=SPHINX CONNECTION="sphinx://localhost:9312/test";
SELECT * FROM t1 WHERE query='test it;mode=any';
109
110. Sphinx search tables
• 1st column: INTEGER UNSIGNED or
BIGINT (document ID)
• 2nd column: match weight
• 3rd column: VARCHAR or TEXT (your
query)
• Query column needs indexing, no other
column needs to be
110
111. What actually happens
• SELECT passes a Sphinx query as the query
column in the WHERE clause
• searchd returns the results
• SphinxSE translates and returns the results
to MariaDB
111
112. SHOW ENGINE
SPHINX STATUS
• Per-query & per-word statistics that searchd returns are accessible via SHOW STATUS
mysql> SHOW ENGINE SPHINX STATUS;
+--------+-------+-------------------------------------------------+
| Type | Name | Status |
+--------+-------+-------------------------------------------------+
| SPHINX | stats | total: 25, total found: 25, time: 126, words: 2 |
| SPHINX | words | sphinx:591:1256 soft:11076:15945 |
+--------+-------+-------------------------------------------------+
2 rows in set (0.00 sec)
112
113. What queries are
supported?
• Most of the Sphinx API is exposed to SphinxSE
• query, mode, sort, offset, limit, index, minid,
maxid, weights, filter, !filter, range, !range,
maxmatches, groupby, groupsort, indexweights,
comment, select
• Sphinx search modes can also be supported via
_sph attributes
• obtain value of @groupby? use ‘_sph_groupby’
113
114. Efficiency
• Allow Sphinx to perform sorting, filtering, and slicing
of result set
• ... as opposed to using WHERE, ORDER BY, LIMIT
clauses on MariaDB
• Why?
• Sphinx optimises and performs better on these
tasks
• Less data packed by searchd, and transferred and
unpacked by SphinxSE
114
115. JOINs
• Perform JOINs on a SphinxSE search table using tables from other engines
SELECT content, date_added FROM test.documents docs
-> JOIN t1 ON (docs.id=t1.id)
-> WHERE query="one document;mode=any";
+-------------------------------------+---------------------+
| content | docdate |
+-------------------------------------+---------------------+
| this is my test document number two | 2006-06-17 14:04:28 |
| this is my test document number one | 2006-06-17 14:04:28 |
+-------------------------------------+---------------------+
2 rows in set (0.00 sec)
115
116. Statistics
• Understand server activity better to understand database loads
•SET GLOBAL userstat=1;
•SHOW CLIENT_STATISTICS; SHOW USER_STATISTICS;
• # of connections, CPU usage, bytes received/sent, row statistics
•SHOW INDEX_STATISTICS; SHOW TABLE_STATISTICS;
• # rows read, changed, indexes
• INFORMATION_SCHEMA.PROCESSLIST has MEMORY_USAGE,
EXAMINED_ROWS (similar with SHOW STATUS output)
116
MariaDB 10.0+
117. Table Elimination
• Resolve a query without accessing some
tables query refers to
• Great for querying highly normalised data
• Basis of “anchor modelling”
• http://www.anchormodeling.com/
• SQL Server 2005/2008, Oracle 11g have it
117
118. Virtual columns
• A column in a table that has its value
automatically calculated either with a pre-
calculated/deterministic expression or values
of other fields in the table
• PERSISTENT (computed when data is inserted
or stored in a table) orVIRTUAL (like aVIEW)
• Similar to MS SQL or Oracle
• https://kb.askmonty.org/en/virtual-columns/
118
124. Extended keys
• Default is extended_keys=on
• Extended Keys, introduced in MariaDB 5.5, is an
optimization which makes use of existing
components of InnoDB/XtraDB keys to generate
more efficient execution plans. Using these
components in many cases allows the server to
generate execution plans which employ index-
only look-ups.
• https://mariadb.com/kb/en/extended-keys/
124
125. NoSQL: HandlerSocket
• Comes with HandlerSocket
• direct access to XtraDB/InnoDB for
CRUD operations
• INSTALL PLUGIN handlersocket
SONAME 'handlersocket.so';
• This allows applications to
communicate more directly with
MySQL storage engines, without the
overhead associated with using SQL.
This includes operations such as
parsing and optimising queries, as
well as table handling operations
(opening, locking, unlocking, closing).
125
126. NoSQL: dynamic
columns
• Allows you to create virtual columns with dynamic content for
each row in table
• Basically a BLOB with handling functions
• Store different attributes for each item (like a web store). Hard to
do relationally
• In MariaDB 10.0: name support (instead of referring to columns by
numbers, name it), convert all dynamic column content to JSON
array, interface with Cassandra
• INSERT INTO tbl SET
dyncol_blob=COLUMN_CREATE("column_name", "value");
• https://kb.askmonty.org/en/dynamic-columns/
126
128. auth_socket
• Authenticates against the Unix socket file
• Uses so_peercred socket option to
obtain information about user running client
•CREATE USER ‘byte’@‘localhost’
IDENTIFIED with auth_socket;
• Refuses connection of any other user but
byte from connecting
128
130. Let’s get somethings
out of the way
• PAM = Pluggable Authentication Module
• Use pam_ldap to to authenticate
credentials against LDAP server —
configure /etc/pam_ldap.conf (you also
obviously need /etc/ldap.conf)
• Simplest way is of course /etc/shadow auth
130
131. MariaDB
INSTALL SONAME ‘auth_pam’;
CREATE USER byte IDENTIFIED via pam
USING ‘mariadb’;
Edit /etc/pam.d/mariadb:
auth required
pam_unix.so
account required
pam_unix.so
131
132. For MySQL
compatibility
• Just use —pam-use-cleartext-
plugin for MySQL to use
mysql_cleartext_password instead of dialog
plugin
132
133. Possible errors
• Connectors don’t support it:
• Client does not support authentication
protocol requested by server; consider
upgrading MySQL client.
• You really have to re-compile connector
using libmysqlclient to have said support
133
135. Why MariaDB 10.0?
• The 5.5 merge took about a year (!)
• We (MariaDB-5.5) have over 1.5 million
lines of extra code with a ~61MB diff
• We didn’t want to repeat this for 5.6
• Also, MySQL 5.6 has a lot of re-factoring,
thus loosing commit history
135
136. In a nutshell
• Built on MariaDB 5.5
• Backported features from MySQL 5.6
• New features
136
137. What about tools?
• SELECTVERSION() will
return 10.0.1-MariaDB
• Oops, we found a bug in
MySQL: https://
mariadb.atlassian.net/
browse/MDEV-4088 &
http://bugs.mysql.com/
bug.php?id=68187
• Still deciding:
• Use 9.0 for a name
• Lie to clients (no)
• Disallow replication
(no)
• Use handshake packet
5.5.30-mysql-10.0.2-
MariaDB without
affectingVERSION() /
@@global.version
137
138. What about tools II?
• Tools really should recognise MariaDB
version as there are already many new
features that MySQL doesn’t have
• eg. HeidiSQL supports virtual columns
(http://www.heidisql.com/forum.php?
t=8671)
138
140. InnoDB & XtraDB
• MariaDB 10.0 ships InnoDB from MySQL 5.6
• MariaDB 10 ships Percona XtraDB as default
• minimal performance improvements expected,
just functionality & features
• bitmap changed page tracking so xtrabackup
can do incremental backups without scanning
all InnoDB files
• SHOW GLOBALVARIABLES LIKE 'innodb_ver%';
140
141. More from MySQL 5.6
• PERFORMANCE_SCHEMA
• InnoDB read-only transactions (TRANSACTION READ
ONLY)
• Optimizer:
• EXISTS-TO-IN optimization
• ORDER BY...LIMIT optimization (show only few rows
of a result set)
• CURRENT_TIMESTAMP as DEFAULT for DATETIME
columns (this is a re-implementation in MariaDB)
141
143. MariaDB 10 replication
• Global Transaction ID
• have complex replication topologies; simple failover & slave promotion
• doesn’t require restarts!
• new slave provisioning: SET GLOBAL GTID_SLAVE_POS =
BINLOG_GTID_POS("masterbin.00045", 600); CHANGE MASTER TO
master_host="192.168.2.4", master_use_gtid=slave_pos; START
SLAVE;
• turning on GTID for slaves: STOP SLAVE
CHANGE MASTER TO master_use_gtid=current_pos; START SLAVE;
• change masters: STOP SLAVE
CHANGE MASTER TO master_host="10.2.3.5"; START SLAVE;
• Crash-safe slaves - GTID position stored in InnoDB table
143
144. Why different GTID
compared to 5.6?
• MySQL 5.6 GTID does not support multi-
source replication
• Supports —log-slave-updates=0 for
efficiency
• Enabled by default
144
145. Binlog (size matters!)
• Example query: INSERT INTO t1VALUES
(10,“foo”);
• MySQL 5.6… 265 bytes
• MariaDB 10.0… 161 bytes
145
146. Crash-safe slave (w/
InnoDB DML)
• Replace non-transactional file relay_log.info
with transactional
mysql.rpl_slave_state
• Changes to rpl_slave_state are
transactionally recovered after crash along
with user data.
146
147. Replication domains
• Keep central concept that replication is just applying events
in-order from a serial binlog stream.
• Allow multi-source replication with multiple active masters
• Let’s the DBA configure multiple independent binlog streams
(one per active master: mysqld --git-domain-id=#)
• Events within one stream are ordered the same across
entire replication topology
• Events between different streams can be in different order
on different servers
• Binlog position is one ID per replication domain
147
148. Parallel replication
• Multi-source replication from different masters executed
in parallel
• Queries from different domains are executed in parallel
• Queries that are run in parallel on the master are run in
parallel on the slave (based on group commit).
• Transactions modifying the same table can be updated
in parallel on the slave!
• Supports both statement based and row based replication.
148
149. Multi-source replication
• Work from Taobao
• Many users partition data across many masters... now you
can replicate many masters to a single slave
• Great for analytical queries, complete backups, etc.
• @@default_master_connection contains current
connection name (used if connection name is not given)
• All master/slave commands take a connection name now
(like CHANGE MASTER “connection_name”, SHOW SLAVE
“connection_name” STATUS, etc.)
• https://kb.askmonty.org/en/multi-source-replication/
149
150. Only in 10.0
• SHOW EXPLAIN for
<thread_id> (https://
mariadb.com/kb/en/show-
explain/) gets the query plan
of a running statement
• EXPLAIN ANALYZE
• Faster ALTER TABLE with
unique keys for Aria &
MyISAM
• Segmented MyISAM
keycaches (up to 64) since
MariaDB 5.2 exist too
• Per-thread memory usage
(Taobao)
• I_S.PROCESSLIST has
MEMORY_USAGE &
EXAMINED_ROWS
• SHOW STATUS has
memory usage too
150
151. SHUTDOWN
• shuts down the server; requires GRANTs
similar to mysqladmin shutdown command
• you can create an event that does a
SHUTDOWN of the server as an
example…
• https://mariadb.com/kb/en/shutdown/
151
153. CassandraSE
• Integration with NoSQL/Big Data DB,Apache Cassandra cluster,
seen as a storage engine to MariaDB
• Combine (join) data between Cassandra & MariaDB
• Write to Cassandra from SQL (SELECT, INSERT, UPDATE,
DELETE)
• CQL is great, but the goal is for you to just work with SQL, not
switch between CQL & SQL
• Data is mapped: rowkey, static columns, dynamic columns
• super columns aren’t supported
• No 1-1 direct map for data types (ref: https://kb.askmonty.org/en/
cassandra-storage-engine/)
153
154. TokuDB
• Opensource - separate MariaDB 5.5+TokuDB/
integrated in 10.0.5
• Improved insert (10-20x faster) & query speed,
compression (up to 90% space reduction),
replication performance and online schema
flexibility
• Uses Fractal Tree Indexes instead of B-Tree
• Tests & builds of TokuDB on multiple platforms
(think greater distribution)
154
155. CONNECT
• CONNECT will speak XML or even grab
data over an ODBC connection
• You can CONNECT to Oracle (via
ODBC), join results from Cassandra (via
CassandraSE) and have all your results sit in
InnoDB
• Turn on engine condition pushdown (10.1
not required)
155
156. SPIDER
• Spider has built-in sharding features
• Partitioning & XA transaction capable
• Different MariaDB instance tables handled
like it is the same instance
156
157. Engine-independent
persistent statistics
• InnoDB has persistent statistics in MySQL
5.6; we have an engine-independent version
• These statistics aren’t limited by the SE API,
and are used by query optimizer to choose
best execution plan for each statement
• Statistics collected for non-indexed
columns too (unlike InnoDB’s)
157
158. MariaDB 10.0.2
• Support for atomic writes on FusionIO
DirectFS
• Optimizer collects & can use histogram-based
statistics for non-indexed columns
• Better table discovery, so FederatedX has
assisted discovery, Sequence engine (creates
ascending/descending sequences, useful in joins)
• SHOW PLUGINS SONAME;
158
159. MariaDB 10.0.4
• SPIDER storage engine for database sharding
merged
• Audit plugin
• complete PERFORMANCE_SCHEMA
• INFORMATION_SCHEMA with upstream
defaults too
• Online ALTER for InnoDB and thread
information for in-place operations
159
160. MariaDB 10.0.5
• Parallel replication - https://mariadb.com/
kb/en/parallel-replication/
• automatically detect independent
transactions, parallel within same table,
adapts to master load, and preserves
commit ordering
• EXPLAIN in the slow query log
160
161. MariaDB 10.0.6
• Serious incompatibility and data corruption
of DATETIME and DATE types due to
get_innobase_type_from_mysql_type
refactor combined with InnoDB Online DDL
• https://mariadb.atlassian.net/browse/
MDEV-5248
• Fixed upgrades from MySQL 5.1 -> MariaDB
• Parallel replication improvements
161
162. MariaDB 10.0.7
• Mostly bug fixes, to stabilise the code
• XtraDB 5.6 merged (InnoDB still default)
• OQGraph v3 - stores data on disk,
persistent, larger graph support
• INFORMATION_SCHEMA.METADATA_L
OCK_INFO plugin to see active metadata
locks
162
163. PCRE Regular
Expressions
• Powerful REGEXP/RLIKE operator
• New operators:
• REGEXP_REPLACE(sub,pattern,replace)
• REGEXP_INSTR(sub,pattern)
• REGEXP_SUBSTR(sub,pattern)
• Works with multi-byte character sets that
MariaDB supports, including East-Asian sets
163
164. Roles
• Bundles users together, with similar
privileges - follows the SQL standard
CREATE ROLE audit_bean_counters;
GRANT SELECT ON accounts.* to
audit_bean_counters;
GRANT audit_bean_counters to
ceo;
164
165. MariaDB 10.0.9 (RC)
• InnoDB 5.6.15 (XtraDB
default; InnoDB plugin)
• Extended keys
optimization on by
default
• MASTER_GTID_WAIT(
) + @@last_gtid
• TIME casted to
DATETIME, date is
CURRENT_DATE not
0000-00-00 - SQL
standards compliant
• @@old_mode=ZER
O_DATE_TIME_CAS
T
165
166. MariaDB 10.0.10 (GA)
• audit plugin now ships
• XtraDB performance fixed incorrect
calculation of flushed pages
• TokuDB compression is now
TOKUDB_ZLIB
• Engine independent table statistics
improved
166
168. Galera Cluster
integrated
• Full integration of Galera Cluster 3.9 (will be 4) into
MariaDB 10.1 — it won’t be a separate download
• no lost transactions
• optimisations for WAN replication
• non-blocking DDL
• no limits on transaction size
•Server version: 10.1.3-MariaDB-wsrep MariaDB
Server, wsrep_25.10.r4144
• Granular monitoring in INFORMATION_SCHEMA —
WSREP_MEMBERSHIP, WSREP_STATUS
168
169. Encryption
• Encryption: tablespace and table level encryption with
support for rolling keys using the AES algorithm
• table encryption — PAGE_ENCRYPTION=1
• tablespace encryption — encrypts everything including
log files
• New file_key_management_filename,
file_key_management_filekey,
file_key_management_encryption_algorithm
• Well documented — https://mariadb.com/kb/en/mariadb/
data-at-rest-encryption/
169
170. Encryption II
• The key file contains encryption keys
identifiers (32-bit numbers) and hex-
encoded encryption keys (128-256 bit
keys), separated by a semicolon.
• don’t forget to create keys!
• eg. openssl enc -aes-256-cbc -
md sha1 -k secret -in
keys.txt -out keys.enc
170
173. Encryption IV
• Tablespace encryption (Google)
• again, you need to pick an encryption algorithm
• specify what to encrypt: innodb-encrypt-tables,
aria, aria-encrypt-tables, encrypt-
tmp-disk-tables, innodb-encrypt-log
• don’t forget key rotation:
•innodb-encryption-threads=4
•innodb-encryption-rotate-key-
age=1800
173
174. EncryptionV
• we also have tablespace scrubbing
• background process that regularly scans
through the tables and upgrades the
encryption keys
• scrubbing works for tablespaces and logs
• —encrypt-tmp-files
• —encrypt-binlog
174
175. EncryptionVI
•/etc/my.cnf.d/enable_encryption.preset
• Consider using Eperi Gateway for Databases
• MariaDB Enterprise has a plugin for Amazon Key
Management Server (KMS)
• mysqlbinlog has no way to read (i.e. decrypt) an
encrypted binlog
• This does not work with MariaDB Galera Cluster yet
(gcache is not encrypted yet), and also xtrabackup needs
additional work (i.e. if you encrypt the redo log)
175
176. Optimistic parallel
replication
• Before, transactions committed in parallel on the
master could be run in parallel
• Now, more than one transaction will be
considered to be run in parallel giving another
performance boost in master-to-slave replication
• We have to check if this only will work with a 10.1
master
• Isn’t fully pushed (or documented) yet — see:
https://mariadb.atlassian.net/browse/MDEV-6676
176
178. InnoDB improvements
• Multi-threaded flush (also in 5.7, different
implementation)
• Page compression (optimised for Flash, SSD, FusionIO)
• 64KB pages in InnoDB (old limit = 16KB).
• Defragementation (FB, backported by DaumKakao)
• Forced primary key
• If option is true, create table without primary key or
unique key where all keyparts are NOT NULL is not
accepted. Instead an error message is printed.
178
179. InnoDB WebScaleSQL
• MDEV-6936: Buffer pool list scan optimisation
• MDEV-6929: Port Facebook Prefix Index Queries Optimization
• MDEV-6932: Enable Lazy Flushing
• MDEV-6931: Page cleaner should do LRU flushing regardless of server
activity
• fixes mysql#71988, mysql#70500
• DB-746 merge clustering key is covering key for mariadb 10 (TokuDB)
• MDEV-6933: Spurious lock_wait_timeout_thread wakeup in
lock_wait_suspend_thread()
• fixes mysql#72123
179
180. Per query variables
• Long history (http://www.bytebot.net/blog/
archives/2014/05/04/per-query-variable-
settings-in-mysqlpercona-
serverwebscalesql)
•SET STATEMENT
max_statement_time=1000 FOR
SELECT name FROM name ORDER
BY name;
180
181. Statement timeouts
• from Twitter patch; re-written by monty
• MAX_STATEMENT_TIME to abort long
running queries
• We call it “query timeouts” + have a
different syntax
• https://mariadb.atlassian.net/browse/
MDEV-4427
181
182. Optimiser
enhancements
• UNION ALL without temporary tables (5.7)
• Improve ORDER BY in optimiser
• Mostly there is EXPLAIN JSON (like 5.6)*
• EXPLAIN ANALYZE with FORMAT=JSON
• includes data from the query execution itself —
this is MariaDB only
• https://mariadb.com/kb/en/mariadb/analyze-
formatjson-examples/
182
184. WebScaleSQL
• WebScaleSQL improvements
• https://mariadb.atlassian.net/browse/
MDEV-6039
• Lots of running thru AddressSanitizer
(ASan)
• Many of these also get backported to
10.0.13
184
185. Passwords
• Password validation plugin exists now
• https://mariadb.com/kb/en/mariadb/development/mariadb-
internals-documentation/password-validation/
• simple_password_check password validation plugin
• can enforce a minimum password length and guarantee that a
password contains at least a specified number of uppercase
and lowercase letters, digits, and punctuation characters.
• cracklib_password_check password validation plugin
• Allows passwords that are strong enough to pass CrackLib
test.This is the same test that pam_cracklib.so does
185
186. Audit plugin
improvements
• Monitor access, locate errors, etc.
• Connection — connect/disconnect/failed;
Query — DDL/DML+TCL/DCL; Object —
Database/Tables
• Passwords in 1.2 replaced by a placeholder
(filtered, i.e. not in audit log)
186
187. CONNECT
• CONNECT having full JSON/BSON support
• Can read filename.json files with ease
• Writing — INSERT, UPDATE, DELETE is
supported — however, if you have added/
modified values for objects or arrays, there
can be complications (similar like the XML
type object issue)
• Works with Sveta’s JSON UDFs as well
187
188. Other bits
• Slaves can execute triggers now
• Dump thread enhancements (remove binlog
lock LOCK_log) from 5.7 included (Google)
• CREATE or REPLACE for most database
objects minus indexes
• SET DEFAULT ROLE (there is a default role
now for current user)
188
189. Other bits
• FRM files are now not created for temporary
tables
• INFORMATION_SCHEMA.SYSTEM_VARIABLES
- information for system variables
• Compiled with security hardening options (fortify
source - https://mariadb.atlassian.net/browse/
MDEV-5730)
• @@sql_log_slow can now be controlled on a
session basis (not just globally)
189
190. GIS
• Full compliance for the OGC standards around GIS.
• yes, we are missing a few functions, but its likely to
improve
• MDEV-4045 Missing OGC Spatial functions.
• MDEV-60 Support for Spatial Reference systems for the
GIS data.
• MDEV-12 OpenGIS: create required tables:
GeometryColumns, related views.
• Speaking shortly, the MariaDB GIS part is now OpenGIS
compliant, and passes all the OpenGIS conformance tests
190
191. Kerberos/GSSAPI
• Every participant in authenticated communication is
known as a ‘principal’ (w/unique name)
• Principals belong to administrative groups called
realms. Kerberos Distribution Centre maintains a
database of principal in realm + associated secret keys
• Client requests a ticket from KDC for access to a
specific asset. KDC uses the client’s secret and the
server’s secret to construct the ticket which allows
the client and server to mutually authenticate each
other, while keeping the secrets hidden.
191
192. MariaDB Kerberos
plugin
• User principals: <username>@<KERBEROS
REALM>
•CREATE USER 'byte' IDENTIFIED VIA
kerberos AS ‘byte/mariadb@lp';
• so that is <username>/
<instance>@<KERBEROS REALM>
• Store Service Principal Name (SPN) is an option
in a config file
192
193. Works where?
• GSSAPI-based Kerberos widely used &
supported on Linux
• Windows supports SSPI authentication and
the plugin supports it
• Comes with MariaDB Server 10.1
193
194. Show list of compiled-
in locales
• INSTALL SONAME 'locales';
SELECT * FROM INFORMATION_SCHEMA.LOCALES;
+-----+-------+-------------------------------------+-----------------------
+---------------------+---------------+--------------+------------------------+
| ID | NAME | DESCRIPTION | MAX_MONTH_NAME_LENGTH |
MAX_DAY_NAME_LENGTH | DECIMAL_POINT | THOUSAND_SEP | ERROR_MESSAGE_LANGUAGE |
+-----+-------+-------------------------------------+-----------------------
+---------------------+---------------+--------------+------------------------+
| 0 | en_US | English - United States | 9 |
9 | . | , | english |
| 1 | en_GB | English - United Kingdom | 9 |
9 | . | , | english |
| 2 | ja_JP | Japanese - Japan | 3 |
3 | . | , | japanese |
194
195. Still use the query
cache?
• Show the contents of the query cache
• Querying the table acquires the QC lock, so lock
waits for queries using/expiring QC
• INSTALL PLUGIN query_cache_info SONAME
‘query_cache_info';
• select statement_schema, statement_text,
result_blocks_count,
• result_blocks_size from
information_schema.query_cache_info;
195
197. Compatibility
• Temporary tables are stored in Aria but now there
is a —default-tmp-storage-engine option
• engine_condition_pushdown flag removed (its
always on for engines that support it)
• --mysql56-temporal-format option to use the
MySQL-5.6 low level formats to store TIME,
DATETIME and TIMESTAMP types
• PERFORMANCE_SCHEMA disabled by default
like in 10.0
197
199. Looking forward to
MariaDB Server 10.2
• mysqlbinlog streaming server backup
• Window functions
• CREATE USER for limiting resource usage
• Virtual column improvements
• EXPLAIN JSON gets better
• Common Table Expressions
199
200. Support
• Five years from every release
• MariaDB 5.5 in Red Hat Enterprise Linux 7
• MariaDB 10 in SUSE Enterprise Linux 12
200
201. Benchmarks
• “Lies, damned lies, and statistics” - Mark Twain
• http://blog.mariadb.org/sysbench-oltp-
mysql-5-6-vs-mariadb-10-0/
• http://dimitrik.free.fr/blog/archives/2013/02/
mysql-performance-mysql-56-vs-mysql-55-
vs-mariadb-55.html
• One thing is clear: there needs to be more
benchmarking done
201
202. MariaDB deployed
“MariaDB had these same bugs that we ran into with
MySQL. However the big difference was that when we
reported these bugs, they were quickly resolved within 48
hours!” -- Dreas van Donselaar, Chief Technology Officer,
SpamExperts
B.V. after migrating over 300 servers from MySQL 5.0
to MariaDB 5.1.
“Migrating from MySQL 5.1 to MariaDB 5.2 was as simple
as removing MySQL RPMs and installing the MariaDB
packages, then running mysql_upgrade.” - Panayot Belchev,
proprietor, Host Bulgaria on providing
MariaDB to over 7,000 of their web hosting customers.
“We made the switch on Saturday --
and we’re seeing benefits already -- our
daily optimization time is down from
24 minutes to just 4 minutes” -- Ali
Watters, CEO, travelblog.org
happy users: pap.fr, Paybox Services, OLX, Jelastic,
Web of Trust,Wikipedia, Craigslist, etc.
“@nginxorg & @mariadb
have helped me save
$12000/year in
infrastructure cost. I love it!
Do more with less!” -
Ewdison Then, CEO,
Slashgear
We upgraded the support.mozilla.org
databases from Percona 5.1 to MariaDB 5.5.
One of the engineers and I had a
conversation where he mentioned that “one
of our worst performing views on SUMO is
doing waaaayyy better with the upgraded
databases”, that it “seems more stable” and
that “I stopped receiving ‘MySQL went away
or disconnected emails’ which came in once
in a while.” - Sheeri Cabral, Mozilla IT
202
204. Books!
1. MariaDB Crash Course, Ben Forta (September 2011)
2. Getting Started with MariaDB, Daniel Bartholomew (October 2013)
3. MariaDB Cookbook, Daniel Bartholomew (March 2014)
4. Real MariaDB, Matt Lee (April 2014)
5. Building a Web Application with PHP & MariaDB:A Reference Guide,
Sai Srinivas Sriparasa (June 2014)
6. MariaDB: Beginners Guide, Rodrigo Ribeiro (August 2014)
7. Mastering MariaDB, Federico Razzioli (September 2014)
8. MariaDB High Performance, Pierre Mavro (September 2014)
9. Learning MySQL & MariaDB, Russell Dyer (April 2015)
204