Hi,
I this related to this issue reported in github :
https://github.com/openlink/virtuoso-opensource/issues/80 ?
Best,
Julien
- Mail original -
> De: virtuoso-users-requ...@lists.sourceforge.net
> À: virtuoso-users@lists.sourceforge.net
> Envoyé: Lundi 23 Septembre 2013 03:16:48
>
Hi Hugh,
I have just solved. The problem was tha I was not accesing to the command
vituoso-t in bin subfolder of virtuoso installation to start the instace.
Instead of that I was installing virtuoso-opensource-6.1-bin, so I was
starting another virtuoso, not what I had installed from the branch.
The CPU utilization for the virtuoso-t process dropped back down once I
returned after a while. As a quick experiment, I ran the SPARQL query:
select distinct ?g where {graph ?g {?s ?p ?o}}
which drove virtuoso-t to 100% utilization which then timed out
returning the CPU back to baseline. Tryi
On 9/22/13 2:40 PM, Erich Bremer wrote:
Hi Kingsley,
My statement about the triple count SPARQL query was only to state
that my virtuoso wasn't frozen for other queries. Historically, for
all of my virtuoso 6.x installs:
select distinct ?g where {graph ?g {?s ?p ?o}}
and
select count(*)
Hi Kingsley,
My statement about the triple count SPARQL query was only to state
that my virtuoso wasn't frozen for other queries. Historically, for all
of my virtuoso 6.x installs:
select distinct ?g where {graph ?g {?s ?p ?o}}
and
select count(*) as ?cc where {?s ?p ?o}
have always work
Hi Hugh,
I shutdown virtuoso and deleted the database and re-ran the upload
with 8 loaders the same way I did. Low and behold, the problem
re-occurred the same way. Here is your status() below. I also checked
top and virtuoso-t is at 100% at the moment. I'm not going to restart
the se
On 9/22/13 8:32 AM, Hugh Williams wrote:
a) select distinct ?g where {graph ?g {?s ?p ?o}}
from the SPARQL endpoint and it timed out.
however, the following query against http://www.geonames.org would work
in a second:
b) select count(*) as ?cc where {?s ?p ?o}
The issue is that listing all
Hi Erich,
Is this condition reproducible as a restart of the server seems to have
resolved it ? As it would be interesting to see what the "status();" command
reports as to the status of the Virtuoso server when in this state ...
Best Regards
Hugh Williams
Professional Services
OpenLink Softwa
