As soon as I killed the cassandra process, the CPU usage plummeted. So at least I know who the culprit was. I'll just start Gremlin Server directly (configured to us BDB), instead of using JanusGraph.sh. 

On Thursday, 17 August 2017 19:22:51 UTC+1, Robert Dale wrote:

For how long does the cpu remain high after you get the `gremlin>` prompt?

Robert Dale

On Thu, Aug 17, 2017 at 2:20 PM, 'Ray Scott' via JanusGraph users list <janu...@...> wrote:

Hi, 

I'm trying to get JanusGraph running on my laptop (MacBook Air 2 Core Intel i7, 8GB) so that I can develop a small working prototype. 

I've gone for the janusgraph.sh method of starting the server and everything is fine until I open a gremlin shell. Then I see the CPU usage for my terminal rocket up past 350%. Once I close the gremlin shell, the CPU usage remains at the same high level, indefinitely. I've tried launching with the Berkeley DB option and no Elastic Search, but I get the exact same behaviour. 

Is there something I can do to stop this from using most of my CPU, or do I just have to live with it? 

Is there a "lite" recommended setup that someone has had success with in the past? 

Thanks. 

--
You received this message because you are subscribed to the Google Groups "JanusGraph users list" group.
To unsubscribe from this group and stop receiving emails from it, send an email to janusgraph-use...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "JanusGraph users list" group.
To unsubscribe from this group and stop receiving emails from it, send an email to janusgraph-users+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.