ActiveMQ Artemis 2.27.1 Documentationproperty name used to identify a scheduled message is "_AMQ_SCHED_DELIVERY" (or the constant Message.HDR_SCHEDULED_DELIVERY_TIME ). The specified value must be a positive long corresponding to the time to configure an LVQ then the default property "_AMQ_LVQ_NAME" is used (or the constant Message.HDR_LAST_VALUE_NAME from the Core API). For example, using the sample configuration HDR_GROUP_ID ). Alternatively, you can set autogroup to true on the SessionFactory which will pick0 码力 | 414 页 | 6.20 MB | 1 年前3- Apache ActiveMQ Artemis 2.30.0 User Manualproperty name used to identify a scheduled message is "_AMQ_SCHED_DELIVERY" (or the constant Message.HDR_SCHEDULED_DELIVERY_TIME ). The specified value must be a positive long corresponding to the time to configure an LVQ then the default property "_AMQ_LVQ_NAME" is used (or the constant Message.HDR_LAST_VALUE_NAME from the Core API). For example, using the sample configuration HDR_GROUP_ID ). Alternatively, you can set autogroup to true on the SessionFactory which will pick0 码力 | 500 页 | 6.37 MB | 1 年前3
- Apache ActiveMQ Artemis 2.26.0 User Manualproperty name used to identify a scheduled message is "_AMQ_SCHED_DELIVERY" (or the constant Message.HDR_SCHEDULED_DELIVERY_TIME ). The specified value must be a positive long corresponding to the time to configure an LVQ then the default property "_AMQ_LVQ_NAME" is used (or the constant Message.HDR_LAST_VALUE_NAME from the Core API). For example, using the sample configuration HDR_GROUP_ID ). Alternatively, you can set autogroup to true on the SessionFactory which will pick0 码力 | 487 页 | 6.28 MB | 1 年前3
- Apache ActiveMQ Artemis 2.28.0 User Manualproperty name used to identify a scheduled message is "_AMQ_SCHED_DELIVERY" (or the constant Message.HDR_SCHEDULED_DELIVERY_TIME ). The specified value must be a positive long corresponding to the time to configure an LVQ then the default property "_AMQ_LVQ_NAME" is used (or the constant Message.HDR_LAST_VALUE_NAME from the Core API). For example, using the sample configuration HDR_GROUP_ID ). Alternatively, you can set autogroup to true on the SessionFactory which will pick0 码力 | 494 页 | 6.33 MB | 1 年前3
- Apache ActiveMQ Artemis 2.22.0 User Manualproperty name used to identify a scheduled message is "_AMQ_SCHED_DELIVERY" (or the constant Message.HDR_SCHEDULED_DELIVERY_TIME ). The specified value must be a positive long corresponding to the time to configure an LVQ then the default property "_AMQ_LVQ_NAME" is used (or the constant Message.HDR_LAST_VALUE_NAME from the Core API). For example, using the sample configuration HDR_GROUP_ID ). Alternatively, you can set autogroup to true on the SessionFactory which will pick0 码力 | 502 页 | 6.34 MB | 1 年前3
- Apache ActiveMQ Artemis 2.29.0 User Manualproperty name used to identify a scheduled message is "_AMQ_SCHED_DELIVERY" (or the constant Message.HDR_SCHEDULED_DELIVERY_TIME ). The specified value must be a positive long corresponding to the time to configure an LVQ then the default property "_AMQ_LVQ_NAME" is used (or the constant Message.HDR_LAST_VALUE_NAME from the Core API). For example, using the sample configuration HDR_GROUP_ID ). Alternatively, you can set autogroup to true on the SessionFactory which will pick0 码力 | 499 页 | 6.37 MB | 1 年前3
- Apache ActiveMQ Artemis 2.21.0 User Manualproperty name used to identify a scheduled message is "_AMQ_SCHED_DELIVERY" (or the constant Message.HDR_SCHEDULED_DELIVERY_TIME ). The specified value must be a positive long corresponding to the time to configure an LVQ then the default property "_AMQ_LVQ_NAME" is used (or the constant Message.HDR_LAST_VALUE_NAME from the Core API). For example, using the sample configuration HDR_GROUP_ID ). Alternatively, you can set autogroup to true on the SessionFactory which will pick0 码力 | 503 页 | 6.34 MB | 1 年前3
- Apache ActiveMQ Artemis 2.23.1 User Manualproperty name used to identify a scheduled message is "_AMQ_SCHED_DELIVERY" (or the constant Message.HDR_SCHEDULED_DELIVERY_TIME ). The specified value must be a positive long corresponding to the time to configure an LVQ then the default property "_AMQ_LVQ_NAME" is used (or the constant Message.HDR_LAST_VALUE_NAME from the Core API). For example, using the sample configuration HDR_GROUP_ID ). Alternatively, you can set autogroup to true on the SessionFactory which will pick0 码力 | 503 页 | 6.35 MB | 1 年前3
- Apache ActiveMQ Artemis 2.32.0 User Manualisn’t designed for easy latency comparisons, however the perf commands expose --hdr <hdr file name> parameter to produce a HDR Histogram compatible report that can be opened with different visualizers + HdrHistogram Log Analyzer as HDR Histogram visualizer tool. Below is the visualization of the HDR histograms collected while adding to the previous benchmark --hdr /tmp/non_durable_queue.hdr Whole test execution perceived sent rate, by setting: --rate 30000 --hdr /tmp/30K.hdr The whole command is then: $ ./artemis perf client --rate 30000 --hdr /tmp/30K.hdr --warmup 20 --max-pending 100 --show-latency --url0 码力 | 528 页 | 10.88 MB | 1 年前3
- Apache ActiveMQ Artemis 2.31.1 User Manualisn’t designed for easy latency comparisons, however the perf commands expose --hdr <hdr file name> parameter to produce a HDR Histogram compatible report that can be opened with different visualizers + HdrHistogram Log Analyzer as HDR Histogram visualizer tool. Below is the visualization of the HDR histograms collected while adding to the previous benchmark --hdr /tmp/non_durable_queue.hdr Whole test execution perceived sent rate, by setting: --rate 30000 --hdr /tmp/30K.hdr The whole command is then: $ ./artemis perf client --rate 30000 --hdr /tmp/30K.hdr --warmup 20 --max-pending 100 --show-latency --url0 码力 | 525 页 | 10.75 MB | 1 年前3
共 46 条
- 1
- 2
- 3
- 4
- 5