In Java, having low memory usually affects the CPU usage, since the garbage collector must run more often, and 1GB heap size seems low to me. I would try to increase the heap size of the workers, and assign a great part of it to the new generation garbage collector (With -Xmx, -Xms, -XX:NewSize and -XX:NewSizeMax). Try different values until you find those that are useful to you. I'd recommend you to try something like 6 GB Heap size and 4 GB NewSize to see if that's the issue, and if after you apply those changes the issue dissapears, then I'd recommend you to decrease those values until you get comfortable with the result.
2014-07-10 14:45 GMT+02:00 Vladi Feigin <[email protected]>: > before changes yes. Now memory is ok but CPU usage is very high. > do you know what can be a reason? > > > On Thu, Jul 10, 2014 at 3:12 PM, 唐思成 <[email protected]> wrote: > >> >> I think is the zero mq has cosumed so many memory >> >> 2014-07-10 >> ------------------------------ >> 唐思成 >> ------------------------------ >> *发件人：* Vladi Feigin >> *发送时间：* 2014-07-09 19:36:33 >> *收件人：* user >> *抄送：* >> *主题：* Storm topology consumes 100% of memory >> Hi, >> >> Our topology consumes almost 100% on the physical machines where it runs. >> We have heavy load ( 5K events per sec) . >> The Java Heap is configured with -Xmx1024m >> But Linux top command shows very large figures (for the Storm process) : >> VIRT=14G >> RES=10G !! >> Apparently that Java code (topology code) doesn't consumes it. So the >> question is which Storm part does consume it? And why? >> What should we check , reconfigure to avoid this? What we do wrong? >> >> At some point we get OOME in the bolts ... >> The Storm version is 0.8.2 >> >> Thank you in advance, >> Vladi >> >> >> >> >> >> >> > -- Carlos Rodríguez Developer at ENEO Tecnología http://redborder.net/ http://lnkd.in/bgfCVF9
