2008/5/18 mark yoffe <[EMAIL PROTECTED]>: > I want to to create a configuration of hundreds to thousands of "consumers" > and "producers" most > will be c++ clients some will be jms clients and in the future when the .net > will support trunk i will use it as well (that the dream at least)
OK, and what throughput and latency do you need for each client? What is your average (real world) message size? I take it that this is all transient pub/sub messaging? > i dont wont to losse even one message meanning i dont want to create a > situation where more data is beaing pushed in than is beaing pulled out > (there might fluxes but over a long time the equilirium will survie - that > the plan) Does this mean that your application is latency sensitive? You mean you are going to throttle your publishers based on the results of empirical testing? Or are you wanting to throttle dynamically based on latency numbers experienced by clients? > while trying to build such a configuration i ofcourse want to achieve a hi > ratio at least the 300K promissed although i saw papers talking about > "planned" performence of 500K and 1M per seconds Who promised 300k? And what is 300k in this context? Where did you see these numbers? > i am curently un able to acheive this even with a semi - empty message ( > amessage containing several characters numbering the message) What is your test doing precisely? I'm afraid I still don't have a clear understanding of your topology or use case, so it is hard to give indications of likely performance or tuning guidelines. RG
