Gnocchi v4 (preview)

•

3 gostaram•657 visualizações

early benchmarks on pre-release Gnocchi v4. includes benchmark comparison between all-ceph v3.x driver versus all-ceph v4 driver. also, shows benchmark using redis+ceph deployment.

Tecnologia

Gnocchi v4 (preview)
gordon chung, gord[at]live.ca

TL;DR (Executive Summary)
Gnocchi v4 accepts incoming measures faster and is more flexible. It also aggregates
measures quicker with less system requirements.
Not bad.

Sack distribution aka. sharding aka.
buckets
- ability to distribute incoming
measures
- enable better distribution on incoming
storage (if applicable)
- better workload scheduling across
metricd workers
Redis driver
- ‘super fast’ storage
- best used for incoming storage
- improved i/o at possible expense of
durability
Ceph driver
- omap-based incoming storage
- leveldb or rocksdb
- reduced tiny object i/o
- Ceph doesn’t like tiny objects
Features

Procedure
1. POST 1000 generic resources spread
across 20 workers, 20 metrics each
a. 20 metrics per POST
b. 1 point/metric per POST
c. 1.2 million points per run, 20K
metrics, 2 granularities x 6
aggregates
2. Wait for backlog to clear
3. Repeat

- Host1 (24Core, 256GB, CentOS)
- OpenStack Controller Node
- Ceph Monitoring service
- Host2 (24Core, 256GB, CentOS)
- OpenStack Compute Node (idle)
- Ceph OSD node (10 OSDs +
SSD Journal)
- 18 metricd
- Host3 (24Core, 256GB, CentOS)
- Ceph OSD node (10 OSDs +
SSD Journal)
- Gnocchi API (32 workers)
- 18 metricd
- Host4 (24Core, 256GB, CentOS)
- OpenStack Compute Node
- Ceph OSD node (10 OSDs +
SSD Journal)
- PostgreSQL
- 18 metricd
v3.x System Overview

- Host1 (24Core, 256GB, CentOS)
- OpenStack Controller Node
- Ceph Monitoring service
- MySQL, Redis
- Host2 (24Core, 256GB, CentOS)
- OpenStack Compute Node (~idle)
- Ceph OSD node (10 OSDs + SSD
Journal)
- Host3 (24Core, 256GB, CentOS)
- OpenStack Compute Node (~idle)
- Ceph OSD node (10 OSDs + SSD
Journal)
- Gnocchi API (32 workers)
- 18 metricd workers
System differences between v3.x and
v4 tests
- 1 less host
- 36 less metricd workers
- 10 less OSDs
- 512 PGs vs 2056 PGs originally
- MySQL instead of PostgreSQL
- for simplicity only
- Gnocchi v4 configured to use 512
sacks, v3.x has essentially 1 sack
v4 System Overview

Notes
● ~8.5x improve POST time vs
v3.x
● v4 Redis incoming ~15%
quicker than v4 Ceph incoming
● Significantly more load on
original v3.x test because of
more metricd workers
● v3.x vs v4 POST under similar
load showed closer performance
but v3.x degraded heavily over
time
POST time

Notes
● ~12x faster at processing
measures
● v4 tests uses ⅓ the number of
metricd processing agents vs
v3.x test
● v4 redis+ceph deployment
~20% improvement compared
to v4 ceph deployment
● v3.x testing with 18 metricd
and 20OSD failed
Aggregation time

Resources
- Homepage - http://gnocchi.xyz
- Github - https://github.com/gnocchixyz

Mais conteúdo relacionado

Mais procurados

Odoo Performance Limits

Odoo

Speakers: Chris Larsen (Limelight Networks) and Benoit Sigoure (Arista Networks) The OpenTSDB community continues to grow and with users looking to store massive amounts of time-series data in a scalable manner. In this talk, we will discuss a number of use cases and best practices around naming schemas and HBase configuration. We will also review OpenTSDB 2.0's new features, including the HTTP API, plugins, annotations, millisecond support, and metadata, as well as what's next in the roadmap.

OpenTSDB 2.0

HBaseCon

A solid backup strategy is a DBA's bread and butter. Cassandra's nodetool snapshot makes it easy to back up the SSTable files, but there remains the question of where to put them and how. Knewton's backup strategy uses Ansible for distributed backups and stores them in S3. Unfortunately, it's all too easy to store backups that are essentially useless due to the absence of a coherent restoration strategy. This problem proved much more difficult and nuanced than taking the backups themselves. I will discuss Knewton's restoration strategy, which again leverages Ansible, yet I will focus on general principles and pitfalls to be avoided. In particular, restores necessitated modifying our backup strategy to generate cluster-wide metadata that is critical for a smooth automated restoration. Such pitfalls indicate that a restore-focused backup design leads to faster and more deterministic recovery. About the Speaker Joshua Wickman Database Engineer, Knewton Dr. Joshua Wickman is currently part of the database team at Knewton, a NYC tech company focused on adaptive learning. He earned his PhD at the University of Delaware in 2012, where he studied particle physics models of the early universe. After a brief stint teaching college physics, he entered the New York tech industry in 2014 working with NoSQL, first with MongoDB and then Cassandra. He was certified in Cassandra at his first Cassandra Summit in 2015.

Cassandra Backups and Restorations Using Ansible (Joshua Wickman, Knewton) | ...

DataStax

OpenTSDB for monitoring @ Criteo

Nathaniel Braun

Cassandra is awesome for many things. One of the things it's awesome for is Time Series. Combining the power of Cassandra with APIs of existing Time Series tools, such as Graphite can yield interesting results. Cyanite is a Time Series aggregator and store built on top of Cassandra. It's fully compatible with Graphite, can serve as a plug-in replacement for Graphite and Graphite web. Cyanite is using SASI indexes to make glob metric path queries, can query and aggregate, store, display and analyse metrics from hundreds and thousands of servers. Which data modelling practices work best for Time Series, which new awesome Cassandra features you can use to make your Time Series analysis better. About the Speaker Alex Petrov Software Engineer, DataStax Polyglot programmer. Interested in algorithms, distributed systems, algebra and high performance solutions.

Building a Fast, Resilient Time Series Store with Cassandra (Alex Petrov, Dat...

DataStax

Pick diamonds from garbage

Tier1 App

"Metrics: Where and How", Vsevolod Polyakov

Yulia Shcherbachova

Developing High Performance Application with Aerospike & Go

Chris Stivers

Update on OpenTSDB and AsyncHBase

HBaseCon

The power of streams in node js

Jawahar

Am I reading GC logs Correctly?

Tier1 App

Slides from #PromCon2018 Munich. https://promcon.io/2018-munich/talks/thanos-prometheus-at-scale/ Bartłomiej Płotka Fabian Reinartz The Prometheus Monitoring system has been thriving for several years. Along with its powerful data model, operational simplicity and reliability have been a key factor in its success. However, some questions were still largely unaddressed to this day. How can we store historical data at the order of petabytes in a reliable and cost-efficient way? Can we do so without sacrificing responsive query times? And what about a global view of all our metrics and transparent handling of HA setups? Thanos takes Prometheus' strong foundations and extends it into a clustered, yet coordination free, globally scalable metric system. It retains Prometheus's simple operational model and even simplifies deployments further. Under the hood, Thanos uses highly cost-efficient object storage that's available in virtually all environments today. By building directly on top of the storage format introduced with Prometheus 2.0, Thanos achieves near real-time responsiveness even for cold queries against historical data. All while having virtually no cost overhead beyond that of the underlying object storage. We will show the theoretical concepts behind Thanos and demonstrate how it seamlessly integrates into existing Prometheus setups.

Thanos - Prometheus on Scale

Bartłomiej Płotka

Мониторинг. Опять, rootconf 2016

Vsevolod Polyakov

Metrics: where and how

Vsevolod Polyakov

Object Storage with Gluster

Gluster.org

1404 app dev series - session 8 - monitoring & performance tuning

MongoDB

Congratulations: you've been selected to build an application that will manage reservations for rooms! On the surface, this sounds simple, but you are building a system for managing a high traffic reservation web page, so we know that a lot of people will be accessing the system. Therefore, we need to ensure that the system can handle all of the eager users that will be flooding the website checking to see what availability each room has. Fortunately, PostgreSQL is prepared for this! And even better, we will be using Postgres 14 to make the problem even easier! We will explore the following PostgreSQL features: * Data types and their functionality, such as: * Data/Time types * Ranges / Multirnages Indexes such as: * GiST * Common Table Expressions and Recursion (though multiranges will make things easier!) * Set generating functions and LATERAL queries * Functions and the PL/PGSQL * Triggers * Logical decoding and streaming We will be writing our application primary with SQL, though we will sneak in a little bit of Python and using Kafka to demonstrate the power of logical decoding. At the end of the presentation, we will have a working application, and you will be happy knowing that you provided a wonderful user experience for all users made possible by the innovation of PostgreSQL!

Build a Complex, Realtime Data Management App with Postgres 14!

Jonathan Katz

Обзор мониторинга в Grammarly, о котором я докладывал на прошлом RootConf'е. Почему мы опять решили всё изменить после перехода на докер, и как мы пришли к zipper-stack, go-carbon, carbon-c-relay (в том числе и бенчмарки альтернативных решений), как получать миллион уникальных метрик в секунду, как мы пришли к тому, что теги в условии безымянных инстансов необходимы, и как мы их сделали, как работает zipper-stack и, вообще, архитектура нашего текущего убер мониторинга.

Путь мониторинга 2.0 всё стало другим / Всеволод Поляков (Grammarly)

Ontico

Galaxy CloudMan performance on AWS

Enis Afgan

Linux Cluster and Distributed Resource Manager

Hong ChangBum

Mais procurados (20)

Odoo Performance Limits

OpenTSDB 2.0

Cassandra Backups and Restorations Using Ansible (Joshua Wickman, Knewton) | ...

OpenTSDB for monitoring @ Criteo

Building a Fast, Resilient Time Series Store with Cassandra (Alex Petrov, Dat...

Pick diamonds from garbage

"Metrics: Where and How", Vsevolod Polyakov

Developing High Performance Application with Aerospike & Go

Update on OpenTSDB and AsyncHBase

The power of streams in node js

Am I reading GC logs Correctly?

Thanos - Prometheus on Scale

Мониторинг. Опять, rootconf 2016

Metrics: where and how

Object Storage with Gluster

1404 app dev series - session 8 - monitoring & performance tuning

Build a Complex, Realtime Data Management App with Postgres 14!

Путь мониторинга 2.0 всё стало другим / Всеволод Поляков (Grammarly)

Galaxy CloudMan performance on AWS

Linux Cluster and Distributed Resource Manager

Semelhante a Gnocchi v4 (preview)

Kubernetes Walk Through from Technical View

Lei (Harry) Zhang

Ceph for Big Science - Dan van der Ster

Ceph Community

QCT Ceph Solution - Design Consideration and Reference Architecture

Ceph Community

QCT Ceph Solution - Design Consideration and Reference Architecture

Patrick McGarry

Testing kubernetes and_open_shift_at_scale_20170209

mffiedler

Ceph Day Beijing: Big Data Analytics on Ceph Object Store

Ceph Community

QuestDB es una base de datos open source de alto rendimiento. Mucha gente nos comentaba que les gustaría usarla como servicio, sin tener que gestionar las máquinas. Así que nos pusimos manos a la obra para desarrollar una solución que nos permitiese lanzar instancias de QuestDB con provisionado, monitorización, seguridad o actualizaciones totalmente gestionadas. Unos cuantos clusters de Kubernetes más tarde, conseguimos lanzar nuestra oferta de QuestDB Cloud. Esta charla es la historia de cómo llegamos ahí. Hablaré de herramientas como Calico, Karpenter, CoreDNS, Telegraf, Prometheus, Loki o Grafana, pero también de retos como autenticación, facturación, multi-nube, o de a qué tienes que decir que no para poder sobrevivir en la nube.

Como creamos QuestDB Cloud, un SaaS basado en Kubernetes alrededor de QuestDB...

javier ramirez

Chotot k8s experiences.pptx

arptit

Build an High-Performance and High-Durable Block Storage Service Based on Ceph

Rongze Zhu

A presentation about the deployment of an ELK stack at bol.com At bol.com we use Elasticsearch, Logstash and Kibana in a logsearch system that allows our developers and operations people to easilly access and search thru logevents coming from all layers of its infrastructure. The presentations explains the initial design and its failures. It continues with explaining the latest design (mid 2014). Its improvements. And finally a set of tips are giving regarding Logstash and Elasticsearch scaling. These slides were first presented at the Elasticsearch NL meetup on September 22nd 2014 at the Utrecht bol.com HQ.

Scaling an ELK stack at bol.com

Renzo Tomà

Deep Dive Into the CERN Cloud Infrastructure - November, 2013

Belmiro Moreira

Ceph Deployment at Target: Customer Spotlight

Red_Hat_Storage

Ceph Deployment at Target: Customer Spotlight

Colleen Corrice

Sanger OpenStack presentation March 2017

Dave Holland

Metal-k8s presentation by Julien Girardin @ Paris Kubernetes Meetup

Laure Vergeron

PGConf.ASIA 2019 Bali - AppOS: PostgreSQL Extension for Scalable File I/O - K...

Equnix Business Solutions

Ceph

Hien Nguyen Van

Après la petite intro sur le stockage distribué et la description de Ceph, Jian Zhang réalise dans cette présentation quelques benchmarks intéressants : tests séquentiels, tests random et surtout comparaison des résultats avant et après optimisations. Les paramètres de configuration touchés et optimisations (Large page numbers, Omap data sur un disque séparé, ...) apportent au minimum 2x de perf en plus.

Ceph: Open Source Storage Software Optimizations on Intel® Architecture for C...

Odinot Stanislas

Hadoop over rgw

zhouyuan

Using OpenStack In a Traditional Hosting Environment

OpenStack Foundation

Semelhante a Gnocchi v4 (preview) (20)

Kubernetes Walk Through from Technical View

Ceph for Big Science - Dan van der Ster

QCT Ceph Solution - Design Consideration and Reference Architecture

Testing kubernetes and_open_shift_at_scale_20170209

Ceph Day Beijing: Big Data Analytics on Ceph Object Store

Como creamos QuestDB Cloud, un SaaS basado en Kubernetes alrededor de QuestDB...

Chotot k8s experiences.pptx

Build an High-Performance and High-Durable Block Storage Service Based on Ceph

Scaling an ELK stack at bol.com

Deep Dive Into the CERN Cloud Infrastructure - November, 2013

Ceph Deployment at Target: Customer Spotlight

Sanger OpenStack presentation March 2017

Metal-k8s presentation by Julien Girardin @ Paris Kubernetes Meetup

PGConf.ASIA 2019 Bali - AppOS: PostgreSQL Extension for Scalable File I/O - K...

Ceph

Ceph: Open Source Storage Software Optimizations on Intel® Architecture for C...

Hadoop over rgw

Using OpenStack In a Traditional Hosting Environment

Último

Bajaj Allianz Life Insurance Company - Insurer Innovation Award 2024

The Digital Insurer

Effective data discovery is crucial for maintaining compliance and mitigating risks in today's rapidly evolving privacy landscape. However, traditional manual approaches often struggle to keep pace with the growing volume and complexity of data. Join us for an insightful webinar where industry leaders from TrustArc and Privya will share their expertise on leveraging AI-powered solutions to revolutionize data discovery. You'll learn how to: - Effortlessly maintain a comprehensive, up-to-date data inventory - Harness code scanning insights to gain complete visibility into data flows leveraging the advantages of code scanning over DB scanning - Simplify compliance by leveraging Privya's integration with TrustArc - Implement proven strategies to mitigate third-party risks Our panel of experts will discuss real-world case studies and share practical strategies for overcoming common data discovery challenges. They'll also explore the latest trends and innovations in AI-driven data management, and how these technologies can help organizations stay ahead of the curve in an ever-changing privacy landscape.

TrustArc Webinar - Unlock the Power of AI-Driven Data Discovery

TrustArc

MySQL Webinar, presented on the 25th of April, 2024. Summary: MySQL solutions enable the deployment of diverse Database Architectures tailored to specific needs, including High Availability, Disaster Recovery, and Read Scale-Out. With MySQL Shell's AdminAPI, administrators can seamlessly set up, manage, and monitor these solutions, ensuring efficiency and ease of use in their administration. MySQL Router, on the other hand, provides transparent routing from the application traffic to the backend servers in the architectures, requiring minimal configuration. Completely built in-house and supported by Oracle, these solutions have been adopted by enterprises of all sizes for their business-critical applications. In this presentation, we'll delve into various database architecture solutions to help you choose the right one based on your business requirements. Focusing on technical details and the latest features to maximize the potential of these solutions.

Mastering MySQL Database Architecture: Deep Dive into MySQL Shell and MySQL R...

Miguel Araújo

MINDCTI Revenue Release Quarter One 2024

MIND CTI

The 7 Things I Know About Cyber Security After 25 Years | April 2024

Rafal Los

A Principled Technologies deployment guide Conclusion Deploying VMware Cloud Foundation 5.1 on next gen Dell PowerEdge servers brings together critical virtualization capabilities and high-performing hardware infrastructure. Relying on our hands-on experience, this deployment guide offers a comprehensive roadmap that can guide your organization through the seamless integration of advanced VMware cloud solutions with the performance and reliability of Dell PowerEdge servers. In addition to the deployment efficiency, the Cloud Foundation 5.1 and PowerEdge solution delivered strong performance while running a MySQL database workload. By leveraging VMware Cloud Foundation 5.1 and PowerEdge servers, you could help your organization embrace cloud computing with confidence, potentially unlocking a new level of agility, scalability, and efficiency in your data center operations.

Deploy with confidence: VMware Cloud Foundation 5.1 on next gen Dell PowerEdg...

Principled Technologies

The presentation explores the development and application of artificial intelligence (AI) from its inception to its current status in the modern world. The term "artificial intelligence" was first coined by John McCarthy in 1956 to describe efforts to develop computer programs capable of performing tasks that typically require human intelligence. This concept was first introduced at a conference held at Dartmouth College, where programs demonstrated capabilities such as playing chess, proving theorems, and interpreting texts. In the early stages, Alan Turing contributed to the field by defining intelligence as the ability of a being to respond to certain questions intelligently, proposing what is now known as the Turing Test to evaluate the presence of intelligent behavior in machines. As the decades progressed, AI evolved significantly. The 1980s focused on machine learning, teaching computers to learn from data, leading to the development of models that could improve their performance based on their experiences. The 1990s and 2000s saw further advances in algorithms and computational power, which allowed for more sophisticated data analysis techniques, including data mining. By the 2010s, the proliferation of big data and the refinement of deep learning techniques enabled AI to become mainstream. Notable milestones included the success of Google's AlphaGo and advancements in autonomous vehicles by companies like Tesla and Waymo. A major theme of the presentation is the application of generative AI, which has been used for tasks such as natural language text generation, translation, and question answering. Generative AI uses large datasets to train models that can then produce new, coherent pieces of text or other media. The presentation also discusses the ethical implications and the need for regulation in AI, highlighting issues such as privacy, bias, and the potential for misuse. These concerns have prompted calls for comprehensive regulations to ensure the safe and equitable use of AI technologies. Artificial intelligence has also played a significant role in healthcare, particularly highlighted during the COVID-19 pandemic, where it was used in drug discovery, vaccine development, and analyzing the spread of the virus. The capabilities of AI in healthcare are vast, ranging from medical diagnostics to personalized medicine, demonstrating the technology's potential to revolutionize fields beyond just technical or consumer applications. In conclusion, AI continues to be a rapidly evolving field with significant implications for various aspects of society. The development from theoretical concepts to real-world applications illustrates both the potential benefits and the challenges that come with integrating advanced technologies into everyday life. The ongoing discussion about AI ethics and regulation underscores the importance of managing these technologies responsibly to maximize their their benefits while minimizing potential harms.

Artificial Intelligence: Facts and Myths

Joaquim Jorge

The value of a flexible API Management solution for Open Banking Steve Melan, Manager for IT Innovation and Architecture - State's and Saving's Bank of Luxembourg Apidays New York 2024: The API Economy in the AI Era (April 30 & May 1, 2024) ------ Check out our conferences at https://www.apidays.global/ Do you want to sponsor or talk at one of our conferences? https://apidays.typeform.com/to/ILJeAaV8 Learn more on APIscene, the global media made by the community for the community: https://www.apiscene.io Explore the API ecosystem with the API Landscape: https://apilandscape.apiscene.io/

Apidays New York 2024 - The value of a flexible API Management solution for O...

apidays

Polkadot JAM Slides - Token2049 - By Dr. Gavin Wood

Juan lago vázquez

This presentation explores the impact of HTML injection attacks on web applications, detailing how attackers exploit vulnerabilities to inject malicious code into web pages. Learn about the potential consequences of such attacks and discover effective mitigation strategies to protect your web applications from HTML injection vulnerabilities. for more information visit https://bostoninstituteofanalytics.org/category/cyber-security-ethical-hacking/

HTML Injection Attacks: Impact and Mitigation Strategies

Boston Institute of Analytics

Tata AIG General Insurance Company - Insurer Innovation Award 2024

The Digital Insurer

Join our latest Connector Corner webinar to discover how UiPath Integration Service revolutionizes API-centric automation in a 'Quote to Cash' process—and how that automation empowers businesses to accelerate revenue generation. A comprehensive demo will explore connecting systems, GenAI, and people, through powerful pre-built connectors designed to speed process cycle times. Speakers: James Dickson, Senior Software Engineer Charlie Greenberg, Host, Product Marketing Manager

Connector Corner: Accelerate revenue generation using UiPath API-centric busi...

DianaGray10

🐬 The future of MySQL is Postgres 🐘

RTylerCroy

How to Troubleshoot Apps for the Modern Connected Worker

ThousandEyes

Scaling API-first – The story of a global engineering organization

Radu Cotescu

A Domino Admins Adventures (Engage 2024)

Gabriella Davis

GenAI Risks & Security Meetup 01052024.pdf

lior mazor

Artificial Intelligence Chap.5 : Uncertainty

Khushali Kathiriya

Abhishek Deb(1), Mr Abdul Kalam(2) M. Des (UX) , School of Design, DIT University , Dehradun. This paper explores the future potential of AI-enabled smartphone processors, aiming to investigate the advancements, capabilities, and implications of integrating artificial intelligence (AI) into smartphone technology. The research study goals consist of evaluating the development of AI in mobile phone processors, analyzing the existing state as well as abilities of AI-enabled cpus determining future patterns as well as chances together with reviewing obstacles as well as factors to consider for more growth.

Exploring the Future Potential of AI-Enabled Smartphone Processors

debabhi2

AWS Community Day CPH - Three problems of Terraform

Andrey Devyatkin

Gnocchi v4 (preview)

1. Gnocchi v4 (preview) gordon chung, gord[at]live.ca

2. TL;DR (Executive Summary) Gnocchi v4 accepts incoming measures faster and is more flexible. It also aggregates measures quicker with less system requirements. Not bad.

3. what’s new

4. Sack distribution aka. sharding aka. buckets - ability to distribute incoming measures - enable better distribution on incoming storage (if applicable) - better workload scheduling across metricd workers Redis driver - ‘super fast’ storage - best used for incoming storage - improved i/o at possible expense of durability Ceph driver - omap-based incoming storage - leveldb or rocksdb - reduced tiny object i/o - Ceph doesn’t like tiny objects Features

5. test methodology

6. Procedure 1. POST 1000 generic resources spread across 20 workers, 20 metrics each a. 20 metrics per POST b. 1 point/metric per POST c. 1.2 million points per run, 20K metrics, 2 granularities x 6 aggregates 2. Wait for backlog to clear 3. Repeat

7. v3.x specifications

8. - Host1 (24Core, 256GB, CentOS) - OpenStack Controller Node - Ceph Monitoring service - Host2 (24Core, 256GB, CentOS) - OpenStack Compute Node (idle) - Ceph OSD node (10 OSDs + SSD Journal) - 18 metricd - Host3 (24Core, 256GB, CentOS) - Ceph OSD node (10 OSDs + SSD Journal) - Gnocchi API (32 workers) - 18 metricd - Host4 (24Core, 256GB, CentOS) - OpenStack Compute Node - Ceph OSD node (10 OSDs + SSD Journal) - PostgreSQL - 18 metricd v3.x System Overview

9. v4 specifications

10. - Host1 (24Core, 256GB, CentOS) - OpenStack Controller Node - Ceph Monitoring service - MySQL, Redis - Host2 (24Core, 256GB, CentOS) - OpenStack Compute Node (~idle) - Ceph OSD node (10 OSDs + SSD Journal) - Host3 (24Core, 256GB, CentOS) - OpenStack Compute Node (~idle) - Ceph OSD node (10 OSDs + SSD Journal) - Gnocchi API (32 workers) - 18 metricd workers System differences between v3.x and v4 tests - 1 less host - 36 less metricd workers - 10 less OSDs - 512 PGs vs 2056 PGs originally - MySQL instead of PostgreSQL - for simplicity only - Gnocchi v4 configured to use 512 sacks, v3.x has essentially 1 sack v4 System Overview

11. results

12.

13. Notes ● ~8.5x improve POST time vs v3.x ● v4 Redis incoming ~15% quicker than v4 Ceph incoming ● Significantly more load on original v3.x test because of more metricd workers ● v3.x vs v4 POST under similar load showed closer performance but v3.x degraded heavily over time POST time

14.

15.

16. Notes ● ~12x faster at processing measures ● v4 tests uses ⅓ the number of metricd processing agents vs v3.x test ● v4 redis+ceph deployment ~20% improvement compared to v4 ceph deployment ● v3.x testing with 18 metricd and 20OSD failed Aggregation time

17. Resources - Homepage - http://gnocchi.xyz - Github - https://github.com/gnocchixyz

Gnocchi v4 (preview)

Recomendados

Recomendados

Mais conteúdo relacionado

Mais procurados

Mais procurados (20)

Semelhante a Gnocchi v4 (preview)

Semelhante a Gnocchi v4 (preview) (20)

Último

Último (20)

Gnocchi v4 (preview)