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.