Because it’s running with simulated data, it will likely consume a lot of CPU as there are always changes going on. Additionally, the view processor is designed to use as much CPU as possible (in terms of allocating threads) as it’s really designed for running on a server. It is possible to limit the number of cores it will try to use - see line 58 of examples-bloomberg/config/fuilstack/fullstack-examplesbloomberg-viewprocessor-spring.xml. The nodesPerCode could be set to e.g. 0.25 or 0.5 rather than 1.
If should however, not be using up a lot of CPU if you don’t have any views running.
What’s happening is that when I’m running with no views, one CPU is eating about 100%. When connect a web browser, it starts to take up 4 CPUs at 100%.
I’ll run this on another platform to see if this is a kernel/java version issue. If not I’ll do a deep dive to see exactly what is causing the CPU to be so high.
One more thing. Is there something of a Null connector. I’d like to run OG with no new data coming in, and I was wondering what the easiest way is of hooking this up.
I found a possible bug in the example server and I just sent up a pull request. What appears to be happening is that a sleep was put in the wrong place.