# 剖析Disruptor为什么会这么快

Martin Fowler在自己网站上写了一篇LMAX架构的文章，在文章中他介绍了LMAX是一种新型零售金融交易平台，它能够以很低的延迟产生大量交易。这个系统是建立在JVM平台上，其核心是一个业务逻辑处理器，它能够在一个线程里每秒处理6百万订单。业务逻辑处理器完全是运行在内存中，使用事件源驱动方式。业务逻辑处理器的核心是Disruptor。

![参考图片](/files/-LlaUCBHMO6Y3z5RsuCZ)

Disruptor它是一个开源的并发框架，并获得2011 Duke’s 程序框架创新奖，能够在无锁的情况下实现网络的Queue并发操作。本文是Disruptor官网中发布的文章的译文（现在被移到了GitHub）。

## 下载

* [pdf](https://legacy.gitbook.com/download/pdf/book/lixiangyun/disruptor)
* [mobi](https://legacy.gitbook.com/download/mobi/book/lixiangyun/disruptor)
* [epub](https://legacy.gitbook.com/download/epub/book/lixiangyun/disruptor)

## 剖析Disruptor为什么会这么快

* [(一) 锁的缺点](/disruptor/readme-1/1.1.md)
* [(二) 神奇的缓存行填充](/disruptor/readme-1/1.2.md)
* [(三) 伪共享](/disruptor/readme-1/1.3.md)
* [(四) 揭秘内存屏障](/disruptor/readme-1/1.4.md)

## Disruptor如何工作和使用

* [(一) Ringbuffer的特别之处](/disruptor/readme-2/2.1.md)
* [(二) 如何从Ringbuffer读取](/disruptor/readme-2/2.2.md)
* [(三) 写入Ringbuffer](/disruptor/readme-2/2.3.md)
* [(四) 解析Disruptor关系组装](/disruptor/readme-2/2.4.md)
* [(五) Disruptor(无锁并发框架)-发布](/disruptor/readme-2/2.5.md)
* [(六) LMAX Disruptor 一个高性能、低延迟且简单的框架](/disruptor/readme-2/2.6.md)
* [(七) Disruptor Wizard已死，Disruptor Wizard永存！](/disruptor/readme-2/2.7.md)
* [(八) Disruptor 2.0更新摘要](/disruptor/readme-2/2.8.md)
* [(九) 线程间共享数据不需要竞争](/disruptor/readme-2/2.9.md)

## Disruptor的应用

* [(一) LMAX的架构](/disruptor/readme-3/3.1.md)
* [(二) 通过Axon和Disruptor处理1M tps](/disruptor/readme-3/3.2.md)

## 转载[自并发编程网](http://ifeve.com)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://lixiangyun.gitbook.io/disruptor/readme-1.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.