1. Messages
  2. ES with JG

Re: ES with JG

Suny <sahithiy...@...>
 

The index is enabled in ES. I verified the same query g.V().has('type',textContains('site'))  by turning on force-index property to true and it works.

The initial hit tool 46000ms and later ones tool 600-750ms.

For the second query - g.V().has('type',textContains('site')).valueMap()

The initial hit tool 129826ms and later ones took 550 - 700ms 

gremlin> :> g.V().has('type',textContains('site')).valueMap().profile()

==>Traversal Metrics

Step                                                               Count  Traversers       Time (ms)    % Dur

=============================================================================================================

JanusGraphStep([],[type.textContains(site)])                        1186        1186          17.913     0.03

  optimization                                                                                 0.203

  backend-query                                                     1186                       5.714

PropertyMapStep(value)                                              1186        1186       64199.498    99.97

                                            >TOTAL                     -           -       64217.412        -




On Friday, September 22, 2017 at 10:17:23 AM UTC-4, Robert Dale wrote:
How much time is 'slow'?.  Are your indexes actually enabled?  What is the byte size of the results? Have you ruled out resource issues - cpu, ram, disk, network?

What does `g.V().has('type',textContains('site')).valueMap().profile()` show?

Robert Dale

On Fri, Sep 22, 2017 at 10:10 AM, Suny <sahi...@...> wrote:
values are of small size. like strings of length 20.

On Friday, September 22, 2017 at 10:03:34 AM UTC-4, Suny wrote:
Each vertex has 3-5 attributes on it. 

On Friday, September 22, 2017 at 9:02:15 AM UTC-4, Jason Plurad wrote:
1500 vertices is a fair amount, but how much data is getting returned in the valueMap? Is there a large number of properties in the map or perhaps are the values very large? Very easily could be the cost of serializing that map. In another post you were asking about string size restrictions...

On Thursday, September 21, 2017 at 2:40:06 PM UTC-4, Suny wrote:
I implemented a mixed index on 'type' attribute on vertex.

Whenever i query for :> g.V().has('type',textContains('car'))

the result comes out really really fast. 

When I do :> g.V().has('type',textContains('site')).valueMap() it is taking so much time to retrieve data. I have 1500 vertices of type car.

Is it because for 1st query it gets the result using ES for the second query it gets vertex id's from ES but for getting attributes it needs to hit JG again ?

Is there a way to fasten up the second query ? 

--
You received this message because you are subscribed to the Google Groups "JanusGraph users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to janusgraph-use...@googlegroups.com.
 To view this discussion on the web visit https://groups.google.com/d/msgid/janusgraph-users/8a3c629b-10c4-4d55-8f8f-8e5397f6ff87%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.
Join {janusgraph-users@lists.lfaidata.foundation to automatically receive all group messages.