This document discusses messaging queues and platforms. It begins with an introduction to messaging queues and their core components. It then provides a table comparing 8 popular open source messaging platforms: Apache Kafka, ActiveMQ, RabbitMQ, NATS, NSQ, Redis, ZeroMQ, and Nanomsg. The document discusses using Apache Kafka for streaming and integration with Google Pub/Sub, Dataflow, and BigQuery. It also covers benchmark testing of these platforms, comparing throughput and latency. Finally, it emphasizes that messaging queues can help applications by allowing producers and consumers to communicate asynchronously.
This document discusses messaging queues and platforms. It begins with an introduction to messaging queues and their core components. It then provides a table comparing 8 popular open source messaging platforms: Apache Kafka, ActiveMQ, RabbitMQ, NATS, NSQ, Redis, ZeroMQ, and Nanomsg. The document discusses using Apache Kafka for streaming and integration with Google Pub/Sub, Dataflow, and BigQuery. It also covers benchmark testing of these platforms, comparing throughput and latency. Finally, it emphasizes that messaging queues can help applications by allowing producers and consumers to communicate asynchronously.
Kvm performance optimization for ubuntuSim Janghoon
This document discusses various techniques for optimizing KVM performance on Linux systems. It covers CPU and memory optimization through techniques like vCPU pinning, NUMA affinity, transparent huge pages, KSM, and virtio_balloon. For networking, it discusses vhost-net, interrupt handling using MSI/MSI-X, and NAPI. It also covers block device optimization through I/O scheduling, cache mode, and asynchronous I/O. The goal is to provide guidance on configuring these techniques for workloads running in KVM virtual machines.
As eBay is moving to OpenStack, we need to find capacity conversion ratio between ESX and KVM. Moreover, we hope to tunning KVM performance that make KVM to be same as or better than ESX
Kvm performance optimization for ubuntuSim Janghoon
This document discusses various techniques for optimizing KVM performance on Linux systems. It covers CPU and memory optimization through techniques like vCPU pinning, NUMA affinity, transparent huge pages, KSM, and virtio_balloon. For networking, it discusses vhost-net, interrupt handling using MSI/MSI-X, and NAPI. It also covers block device optimization through I/O scheduling, cache mode, and asynchronous I/O. The goal is to provide guidance on configuring these techniques for workloads running in KVM virtual machines.
As eBay is moving to OpenStack, we need to find capacity conversion ratio between ESX and KVM. Moreover, we hope to tunning KVM performance that make KVM to be same as or better than ESX
QEMU Disk IO Which performs Better: Native or threads?Pradeep Kumar
Pradeep Kumar Surisetty from Red Hat presented a comparison of native and threaded I/O performance in QEMU disk I/O. He outlined KVM I/O architecture, storage transport options in KVM including virtio-blk configurations, and benchmark tools used. Performance testing was done with various disk types, file systems, images and configurations. Native generally outperformed threads for random I/O workloads, while threads sometimes showed better performance for sequential reads, especially with multiple VMs.
This slide is for Ultimate Agilist Tokyo in Japan. 2012.Nov.
I want to think about agile programmer's skill set. and I want to introduce ICAgile to Japan.
I analyzed agile value, principles, practices and ICAgile.
and participant members created some mandatory skill set in this session.
See this blog entry , that will be better.
http://simple-architect.blogspot.jp/2012/11/agile-programmers-skill-set-ultimate.html
[db tech showcase Tokyo 2016] D24: データベース環境における検証結果から理解する失敗しないフラッシュ活用法 第三章 ~デ...Insight Technology, Inc.
フラッシュのGB単価はHDDと並び、オールフラッシュ導入が加速化する一方、インラインでの重複排除、圧縮機能のオーバーヘッド、メンテナンス / 障害時の影響など、気をつけなければいけない事は沢山あります。本セッションでは、オールフラッシュ製品(Pure Storage)上でOracle Databaseを稼働させた検証結果と生のデモンストレーションをベースに、DB on Pure Storageならではの活用法を考えます。
The document discusses agile architecture and how architecture can support agile development. It defines agile architecture as one that allows quick replacement of details and is easy to verify. An agile architecture enables the principles of the Agile Manifesto by allowing for quick change and being verifiable at any point. Traditional architecture focuses on rules and limitations, while agile architecture is needed to support rapid development, continuous delivery of value, and managing change and complexity. The document outlines practices of agile architecture including having architecture as part of the scrum team and modeling and documenting in an agile fashion. It also discusses roles like the agile architect and characteristics like understanding stakeholders and having a big picture view.
No one can predict unforeseen killer applications enabled by new wireless technologies (e.g., 5G network) beforehand. Looking back 20-year history of mobile wireless network, it has been very tough to prepare killer applications a prior to the emergence of new radio access technologies. NTT DOCOMO’s i-mode was not prepared for 2G always-on network., and invented after that. Smartphones with application markets became popular after the 3G network deployment, for which video conversation had been prepared a a killer service candidate and which didn’t make a success. 4G network brought us more capacity and low latency network, while youtube, hulu, Netflix, facebook messenger and others were natured by such a rich mobile communication environment with cloud platforms.
Everyone, nowadays, are talking about a buzz word “IoT” without having a solid idea for monetization. Such a bold discussion may mislead our radio access technology development to an unpromised land.
My recommendation is “Decide as late as possible, particularly for decisions that are irreversible.” According to software engineering terminology, it says also “late binding.” Don’t rush into a 10Gps broadband network nor a hyper low latency and 0% packet-loss assured network.
Having said that, the 5G beam forming radio technology (enabled by Massive MIMO) will bring a unique communication characteristics with a more reliable, higher capacity and 3D-positioning. My bet on 5G killer applications is “Night Golf” where you can play golf without seeing a ball which is being identified by the 5G radio. haha.
This document discusses 5G and multi-access edge computing (MEC). The key points are: 1) 5G can achieve latency of 100ms while 4G is 300ms, and 5G bandwidth is 20Gbps compared to 4G's 1.29Gbps; 2) MEC deployed close to users on 5G can achieve even lower latency of under 10ms; 3) MEC integrated with 5G can enable new applications for IoT, VR/AR with high speed and low latency.
NTT Docomo's Challenge looking ahead the world pf 5G × OpenStack - OpenStack最...VirtualTech Japan Inc.
タイトル:NTT Docomo's Challenge looking ahead the world pf 5G × OpenStack
アジェンダ:
- Current Challenge
-- DOCOMO Cloud Platform
-- BizDevOps
- Challenge for the future
-- DOCOMO 5G Open Cloud
-- Next Challenge
Here are the key points from the AT&T presentation on their "Network AI" framework:
- AT&T is developing an open source framework called "Network AI" to drive their software-defined network transformation.
- The goal is to apply AI/machine learning techniques to continuously optimize their network performance. This will be done by collecting massive amounts of network data and using it to train ML models.
- As part of this effort, AT&T is contributing several open source projects to the Linux Foundation like Airship, Akraino, and Acumos. Airship provides tools for deploying OpenStack and Kubernetes on the edge, while Akraino is an edge computing framework. Acumos allows for developing and