messaging

Technique or utility to minimize Java “warm-up” time?

若如初见. 提交于 2019-11-26 15:08:26
I am supporting a Java messaging application that requires low latency (< 300 microseconds processing each message). However, our profiling shows that the Sun Java Virtual Machine runs slowly at first, and speeds up after the first 5,000 messages or so. The first 5,000 messages have latency of 1-4 milliseconds. After about the first 5,000, subsequent messages have ~250 microseconds latency, with occasional outliers. It's generally understood that this is typical behavior for a Java application. However, from a business standpoint it's not acceptable to tell the customer that they have to wait

RabbitMQ and relationship between channel and connection

拈花ヽ惹草 提交于 2019-11-26 07:52:52
问题 The RabbitMQ Java client has the following concepts: Connection - a connection to a RabbitMQ server instance Channel - ??? Consumer thread pool - a pool of threads that consume messages off the RabbitMQ server queues Queue - a structure that holds messages in FIFO order I\'m trying to understand the relationship, and more importantly , the associations between them. I\'m still not quite sure what a Channel is, other than the fact that this is the structure that you publish and consume from,

RabbitMQ / AMQP: single queue, multiple consumers for same message?

那年仲夏 提交于 2019-11-26 06:12:41
问题 I am just starting to use RabbitMQ and AMQP in general. I have a queue of messages I have multiple consumers, which I would like to do different things with the same message . Most of the RabbitMQ documentation seems to be focused on round-robin, ie where a single message is consumed by a single consumer, with the load being spread between each consumer. This is indeed the behavior I witness. An example: the producer has a single queue, and send messages every 2 sec: var amqp = require(\'amqp

Technique or utility to minimize Java “warm-up” time?

折月煮酒 提交于 2019-11-26 04:12:18
问题 I am supporting a Java messaging application that requires low latency (< 300 microseconds processing each message). However, our profiling shows that the Sun Java Virtual Machine runs slowly at first, and speeds up after the first 5,000 messages or so. The first 5,000 messages have latency of 1-4 milliseconds. After about the first 5,000, subsequent messages have ~250 microseconds latency, with occasional outliers. It\'s generally understood that this is typical behavior for a Java