<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jun 21, 2017 at 10:13 AM, Ilya Shakhat <span dir="ltr"><<a href="mailto:shakhat@gmail.com" target="_blank">shakhat@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><div>Hi Ken, <br><br></div>Please check scenarios and reports that exist in Performance Docs. In particular you may be interested in:<br></div> * O.M.Simulator - <a href="https://github.com/openstack/oslo.messaging/blob/master/tools/simulator.py" target="_blank">https://github.com/openstack/o<wbr>slo.messaging/blob/master/tool<wbr>s/simulator.py</a> <br> * MQ  performance scenario - <a href="https://docs.openstack.org/developer/performance-docs/test_plans/mq/plan.html#message-queue-performance" target="_blank">https://docs.openstack.org/dev<wbr>eloper/performance-docs/test_<wbr>plans/mq/plan.html#message-<wbr>queue-performance</a><br><div> * One of RabbitMQ reports - <a href="https://docs.openstack.org/developer/performance-docs/test_results/mq/rabbitmq/cmsm/index.html" target="_blank">https://docs.openstack.org/dev<wbr>eloper/performance-docs/test_<wbr>results/mq/rabbitmq/cmsm/index<wbr>.html</a><br></div><div></div><div> * MQ HA scenario - <a href="https://docs.openstack.org/developer/performance-docs/test_plans/mq_ha/plan.html" target="_blank">https://docs.openstack.org/dev<wbr>eloper/performance-docs/test_<wbr>plans/mq_ha/plan.html</a><br></div><div> * One of RabbitMQ HA reports - <a href="https://docs.openstack.org/developer/performance-docs/test_results/mq_ha/rabbitmq-ha-queues/cs1ss2-ks2-ha/omsimulator-ha-call-cs1ss2-ks2-ha/index.html" target="_blank">https://docs.openstack.org/dev<wbr>eloper/performance-docs/test_<wbr>results/mq_ha/rabbitmq-ha-<wbr>queues/cs1ss2-ks2-ha/omsimulat<wbr>or-ha-call-cs1ss2-ks2-ha/<wbr>index.html</a><br><br></div></div></blockquote><div><br></div><div>Thank you Ilya - these tests you reference are indeed valuable.<br><br></div><div>But, IIUC, those tests benchmark queue throughput, using a single (highly threaded) client->single server traffic flow.   If that is the case, I think the tests we're trying to define might be a bit more specific to the FEMDC [0] use cases:  multiple servers consuming from different topics while many clients distributed across the message bus are connecting, generating traffic, failing over, etc.<br><br></div><div>The goal of these tests would be to quantify the behavior of the message bus as a whole under different messaging loads, failure conditions, etc.<br></div><div><br>[0] <a href="https://wiki.openstack.org/wiki/Fog_Edge_Massively_Distributed_Clouds">https://wiki.openstack.org/wiki/Fog_Edge_Massively_Distributed_Clouds</a><br><br><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><br></div><div>Thanks,<br></div><div>Ilya<br></div></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div class="gmail-m_9039078342656745187h5">2017-06-21 15:23 GMT+02:00 Ken Giusti <span dir="ltr"><<a href="mailto:kgiusti@gmail.com" target="_blank">kgiusti@gmail.com</a>></span>:<br></div></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div class="gmail-m_9039078342656745187h5"><div dir="ltr"><div><div><div><div><div>Hi All,<br><br></div>Andy and I have taken a stab at defining some test scenarios for anal the different message bus technologies:<br><br><a href="https://etherpad.openstack.org/p/1BGhFHDIoi" target="_blank">https://etherpad.openstack.org<wbr>/p/1BGhFHDIoi</a><br><br></div>We've started with tests for just the oslo.messaging layer to analyze throughput and latency as the number of message bus clients - and the bus itself - scale out.<br><br></div>The next step will be to define messaging oriented test scenarios for an openstack deployment.  We've started by enumerating a few of the tools, topologies, and fault conditions that need to be covered.<br><br></div>Let's use this epad as a starting point for analyzing messaging - please feel free to contribute, question, and criticize :)<br><br></div>thanks, <br><span class="gmail-m_9039078342656745187m_-1878454181022332452HOEnZb"><font color="#888888"><div><div><div><div><div><div><div><div><div><br><br clear="all"><div><div><div><br>-- <br><div class="gmail-m_9039078342656745187m_-1878454181022332452m_5236066748280472759gmail_signature">Ken Giusti  (<a href="mailto:kgiusti@gmail.com" target="_blank">kgiusti@gmail.com</a>)</div>
</div></div></div></div></div></div></div></div></div></div></div></div></font></span></div>
<br></div></div>______________________________<wbr>______________________________<wbr>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.op<wbr>enstack.org?subject:unsubscrib<wbr>e</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k-dev</a><br>
<br></blockquote></div><br></div>
<br>______________________________<wbr>______________________________<wbr>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.op<wbr>enstack.org?subject:unsubscrib<wbr>e</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k-dev</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br><div class="gmail-m_9039078342656745187gmail_signature">Ken Giusti  (<a href="mailto:kgiusti@gmail.com" target="_blank">kgiusti@gmail.com</a>)</div>
</div></div>