Re: [Bigdata-developers] status page is often unresponsive on query details

SourceForge Headquarters 1320 Columbia Street Suite 310 San Diego, CA 92101 +1 (858) 422-6466

Hum.  Perhaps a tight loop?  Can you put a profiler on it and see where the
time is?

----
Bryan Thompson
Chief Scientist & Founder
SYSTAP, LLC
4501 Tower Road
Greensboro, NC 27410
br...@sy...
http://blazegraph.com
http://blog.blazegraph.com

Blazegraph™ <http://www.blazegraph.com/> is our ultra high-performance
graph database that supports both RDF/SPARQL and Tinkerpop/Blueprints
APIs.  Blazegraph is now available with GPU acceleration using our disruptive
technology to accelerate data-parallel graph analytics and graph query.

CONFIDENTIALITY NOTICE:  This email and its contents and attachments are
for the sole use of the intended recipient(s) and are confidential or
proprietary to SYSTAP. Any unauthorized review, use, disclosure,
dissemination or copying of this email or its contents or attachments is
prohibited. If you have received this communication in error, please notify
the sender by reply email and permanently delete all copies of the email
and its contents and attachments.

On Fri, Nov 20, 2015 at 3:00 PM, Jeremy J Carroll <jj...@sy...> wrote:

> The GC activity looks normal
>
> $ tail -f gc.txt.0.current
> 2015-11-20T11:54:26.679-0800: 165074.286: [GC (Allocation Failure)
> [PSYoungGen: 10972401K->27312K(11192832K)] 15072162K->4127073K(22849024K),
> 0.0327707 secs] [Times: user=0.21 sys=0.00, real=0.03 secs]
> 2015-11-20T11:54:34.087-0800: 165081.693: [GC (Allocation Failure)
> [PSYoungGen: 11022000K->29680K(11201024K)] 15121761K->4129441K(22857216K),
> 0.0393527 secs] [Times: user=0.25 sys=0.01, real=0.04 secs]
> 2015-11-20T11:54:41.544-0800: 165089.150: [GC (Allocation Failure)
> [PSYoungGen: 11024368K->32673K(11217408K)] 15124129K->4132434K(22873600K),
> 0.0377333 secs] [Times: user=0.26 sys=0.01, real=0.04 secs]
> 2015-11-20T11:54:49.104-0800: 165096.710: [GC (Allocation Failure)
> [PSYoungGen: 11075489K->34353K(11225088K)] 15175250K->4134114K(22881280K),
> 0.0329827 secs] [Times: user=0.24 sys=0.00, real=0.03 secs]
> 2015-11-20T11:54:56.496-0800: 165104.102: [GC (Allocation Failure)
> [PSYoungGen: 11077169K->38080K(11241984K)] 15176930K->4137841K(22898176K),
> 0.0379682 secs] [Times: user=0.28 sys=0.00, real=0.04 secs]
> 2015-11-20T11:55:04.088-0800: 165111.694: [GC (Allocation Failure)
> [PSYoungGen: 11128000K->40626K(11249664K)] 15227761K->4140387K(22905856K),
> 0.0394295 secs] [Times: user=0.24 sys=0.01, real=0.04 secs]
> 2015-11-20T11:55:11.895-0800: 165119.502: [GC (Allocation Failure)
> [PSYoungGen: 11130546K->42770K(11266048K)] 15230307K->4142531K(22922240K),
> 0.0362157 secs] [Times: user=0.27 sys=0.00, real=0.04 secs]
> 2015-11-20T11:55:19.572-0800: 165127.178: [GC (Allocation Failure)
> [PSYoungGen: 11177234K->42851K(11273216K)] 15276995K->4145108K(22929408K),
> 0.0377121 secs] [Times: user=0.29 sys=0.01, real=0.03 secs]
> 2015-11-20T11:55:27.087-0800: 165134.694: [GC (Allocation Failure)
> [PSYoungGen: 11177315K->42627K(11290112K)] 15279572K->4147371K(22946304K),
> 0.0383873 secs] [Times: user=0.28 sys=0.01, real=0.04 secs]
> 2015-11-20T11:55:34.844-0800: 165142.450: [GC (Allocation Failure)
> [PSYoungGen: 11217539K->42784K(11296256K)] 15322283K->4150024K(22952448K),
> 0.0383107 secs] [Times: user=0.32 sys=0.00, real=0.04 secs]
> 2015-11-20T11:55:42.521-0800: 165150.128: [GC (Allocation Failure)
> [PSYoungGen: 11217696K->44033K(11310080K)] 15324936K->4153778K(22966272K),
> 0.0389080 secs] [Times: user=0.31 sys=0.00, real=0.04 secs]
> 2015-11-20T11:55:50.160-0800: 165157.766: [GC (Allocation Failure)
> [PSYoungGen: 11252225K->42833K(11315200K)] 15361970K->4155049K(22971392K),
> 0.0511641 secs] [Times: user=0.31 sys=0.01, real=0.05 secs]
>
> Although top shows 780% CPU usage
>
> Wiki page is:
> https://wiki.blazegraph.com/wiki/index.php/REST_API#STATUS
>
>
> $ curl -k https://localhost:2443/bigdata/status?showQueries=details
> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "
> http://www.w3.org/TR/html4/loose.dtd"><html><head><meta
> http-equiv="Content-Type"
> content="text&#47;html;charset=UTF-8"><title>blazegraph&trade; by
> SYSTAP</title
> ></head
> ><body<p>Build Version=<span id="buildVersion">1.5.3-20151114-maint</span
> ></p
> ><p>Accepted query count=<span id="accepted-query-count">12723</span
> ></p
> ><p>Running query count=<span id="running-query-count">2</span
> ></p
> ><p>Show <a
> href="https:&#47;&#47;localhost:2443&#47;bigdata&#47;status?showQueries"
> id="show-queries">queries</a
> >, <a
> href="https:&#47;&#47;localhost:2443&#47;bigdata&#47;status?showQueries=details"
> id="show-query-details">query details</a
> >.</p
> ><p id="counter-set">
> &#47;blockedWorkQueueCount=17
> &#47;blockedWorkQueueRunningTotal=34006865
> &#47;deadlineQueueSize=0
> &#47;operatorActiveCount=41
> &#47;operatorHaltCount=217992594
> &#47;operatorStartCount=217992635
> &#47;operatorTasksPerQuery=5976.001809309721
> &#47;queriesPerSecond=1.7439009838282562
> &#47;queryDoneCount=36478
> &#47;queryErrorCount=15
> &#47;queryStartCount=36484</p
> ></html
> >
>
> is not very helpful !
>
> My gut feel is that this is probably an explore click gone bad ….
>
> com.bigdata.rdf.sail.describeMode SCBD
> com.bigdata.rdf.sail.describeIterationStatementLimit 1000
> com.bigdata.rdf.sail.describeIterationLimit 10
>
> On Nov 20, 2015, at 11:50 AM, Bryan Thompson <br...@sy...> wrote:
>
> What is the current GC activity?  If the server is in GC hell then it will
> not be responsive.
>
> ----
> Bryan Thompson
> Chief Scientist & Founder
> SYSTAP, LLC
> 4501 Tower Road
> Greensboro, NC 27410
> br...@sy...
> http://blazegraph.com
> http://blog.blazegraph.com
>
> Blazegraph™ <http://www.blazegraph.com/> is our ultra high-performance
> graph database that supports both RDF/SPARQL and Tinkerpop/Blueprints
> APIs.  Blazegraph is now available with GPU acceleration using our disruptive
> technology to accelerate data-parallel graph analytics and graph query.
>
> CONFIDENTIALITY NOTICE:  This email and its contents and attachments are
> for the sole use of the intended recipient(s) and are confidential or
> proprietary to SYSTAP. Any unauthorized review, use, disclosure,
> dissemination or copying of this email or its contents or attachments is
> prohibited. If you have received this communication in error, please notify
> the sender by reply email and permanently delete all copies of the email
> and its contents and attachments.
>
> On Fri, Nov 20, 2015 at 2:20 PM, Jeremy J Carroll <jj...@sy...> wrote:
>
>> One of my deployments is under-performing, and I fear that I have a
>> run-away query.
>>
>> I go to the status page, and see:
>>
>>
>> Build Version=1.5.3-20151114-maint
>>
>> Accepted query count=12633
>>
>> Running query count=2
>>
>> Show queries <https://localhost:2443/bigdata/status?showQueries>, query
>> details <https://localhost:2443/bigdata/status?showQueries=details>.
>> /blockedWorkQueueCount=16 /blockedWorkQueueRunningTotal=33211984
>> /deadlineQueueSize=0 /operatorActiveCount=40 /operatorHaltCount=213105698
>> /operatorStartCount=213105738 /operatorTasksPerQuery=5860.348091519085
>> /queriesPerSecond=1.7561494448212958 /queryDoneCount=36364
>> /queryErrorCount=14 /queryStartCount=36370.
>>
>>
>>
>> When I click on either link, nothing happens.
>>
>> This happens fairly frequently, and is not a new issue.
>>
>> 1) Is this known about
>> 2) Is there anything I can do to get a clearer picture of whats happening?
>>
>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>>
>> _______________________________________________
>> Bigdata-developers mailing list
>> Big...@li...
>> https://lists.sourceforge.net/lists/listinfo/bigdata-developers
>>
>>
>
>

Re: [Bigdata-developers] status page is often unresponsive on query details

Fast, scalable, robust graph database platform

Re: [Bigdata-developers] status page is often unresponsive on query details