hepyu commented on issue #614: How much memory should we use for broker and namesrv when using cluster mode? URL: https://github.com/apache/rocketmq/issues/614#issuecomment-448532546 > @hepyu > 1.the namesrv just save broker and topic info, I think they cost memory little, is 16G is too large? I think even 8G is also too large, is this right? > it depends on your topics, 8g is OK.but 2 namesrv is enough. How could I understand "it depends on your topics", is this mean if topics/queues/brokers are too many, the infos will cost much more memory? But will they cost 8g? In other words, I mean , 8g memory of namesrv could hold how many topics/queues/brokers? Just to control the money if biz accept... > 2.About lost message when only using master, is this happen only when master disk is wrong? I mean if we don't consider the disk broken, the rocketmq won't lose message, is this right? > if you use async_flush,when broker crash and message hasn't flush to the disk,then the message lost. yeah, it is, but I think the broker would run stablely at most of the time, if it is and we could accept the little crase case about broker, is this make some sence? And how about the broker crase rate? And What about the disk type? namesrv and broker are all ssd? > 3.If we use slave feature, is it will have some influences about the qps? And How big is the impact? > yes ,but it can gurantee the message reliability Yes, I agree. Just to control the money if biz accept... > 4.And what about the qps when using the config as you advice? > 1.pub message: message size:2K and tps is 40000 > 2.consume message:messages size 2k and tps is 60000. > message size affects TPS. Is this tps running under these resources as you adviced before? 4 cluster,per cluster have 2 master and 2slave. broker : 2M-2S. namesrv-machine: 8cpu and 8g broker-machine: 8cpu and 16g
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
