Hi Everyone,
A little FYI.
We have loaded Wikidata into a Virtuoso instance accessible via SPARQL [1]. One benefit is helping to understand Wikidata using our Faceted Browsing Interface for Entity Relationship Types [2][3].
Links:
[1] http://wikidata.demo.openlinksw.com/sparql -- SPARQL endpoint
[2] http://wikidata.demo.openlinksw.com/fct -- Faceted Browsing Interface
[3] About New York https://wikidata.demo.openlinksw.com/describe/?url=http%3A%2F%2Fwww.wikidata.org%2Fentity%2FQ60&gp=16&go=&lp=940&invfp=IFP_OFF&sas=SAME_AS_OFF&distinct=1
Enjoy!
Feedback always welcome too :)
That is really cool! Thanks and congratulations! I will certainly play with it.
Is it in some way synced or is it a static snapshot?
On Tue, Aug 13, 2019 at 4:10 PM Kingsley Idehen kidehen@openlinksw.com wrote:
Hi Everyone,
A little FYI.
We have loaded Wikidata into a Virtuoso instance accessible via SPARQL [1]. One benefit is helping to understand Wikidata using our Faceted Browsing Interface for Entity Relationship Types [2][3].
Links:
[1] http://wikidata.demo.openlinksw.com/sparql -- SPARQL endpoint
[2] http://wikidata.demo.openlinksw.com/fct -- Faceted Browsing Interface
[3] About New York https://wikidata.demo.openlinksw.com/describe/?url=http%3A%2F%2Fwww.wikidata.org%2Fentity%2FQ60&gp=16&go=&lp=940&invfp=IFP_OFF&sas=SAME_AS_OFF&distinct=1
Enjoy!
Feedback always welcome too :)
-- Regards,
Kingsley Idehen Founder & CEO OpenLink Software Home Page: http://www.openlinksw.com Community Support: https://community.openlinksw.com Weblogs (Blogs): Company Blog: https://medium.com/openlink-software-blog Virtuoso Blog: https://medium.com/virtuoso-blog Data Access Drivers Blog: https://medium.com/openlink-odbc-jdbc-ado-net-data-access-drivers
Personal Weblogs (Blogs): Medium Blog: https://medium.com/@kidehen Legacy Blogs: http://www.openlinksw.com/blog/~kidehen/ http://kidehen.blogspot.com
Profile Pages: Pinterest: https://www.pinterest.com/kidehen/ Quora: https://www.quora.com/profile/Kingsley-Uyi-Idehen Twitter: https://twitter.com/kidehen Google+: https://plus.google.com/+KingsleyIdehen/about LinkedIn: http://www.linkedin.com/in/kidehen
Web Identities (WebID): Personal: http://kingsley.idehen.net/public_home/kidehen/profile.ttl#i : http://id.myopenlink.net/DAV/home/KingsleyUyiIdehen/Public/kingsley.ttl#this
Wikidata mailing list Wikidata@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata
On 8/13/19 7:20 PM, Denny Vrandečić wrote:
That is really cool! Thanks and congratulations! I will certainly play with it.
Is it in some way synced or is it a static snapshot?
At this juncture, it is a snapshot, but ultimately we want something that's kept in sycn, just like DBpedia-Live etc..
Kingsley
On Tue, Aug 13, 2019 at 4:10 PM Kingsley Idehen <kidehen@openlinksw.com mailto:kidehen@openlinksw.com> wrote:
Hi Everyone, A little FYI. We have loaded Wikidata into a Virtuoso instance accessible via SPARQL [1]. One benefit is helping to understand Wikidata using our Faceted Browsing Interface for Entity Relationship Types [2][3]. Links: [1] http://wikidata.demo.openlinksw.com/sparql -- SPARQL endpoint [2] http://wikidata.demo.openlinksw.com/fct -- Faceted Browsing Interface [3] About New York <https://wikidata.demo.openlinksw.com/describe/?url=http%3A%2F%2Fwww.wikidata.org%2Fentity%2FQ60&gp=16&go=&lp=940&invfp=IFP_OFF&sas=SAME_AS_OFF&distinct=1> Enjoy! Feedback always welcome too :) -- Regards, Kingsley Idehen Founder & CEO OpenLink Software Home Page: http://www.openlinksw.com Community Support: https://community.openlinksw.com Weblogs (Blogs): Company Blog: https://medium.com/openlink-software-blog Virtuoso Blog: https://medium.com/virtuoso-blog Data Access Drivers Blog: https://medium.com/openlink-odbc-jdbc-ado-net-data-access-drivers Personal Weblogs (Blogs): Medium Blog: https://medium.com/@kidehen Legacy Blogs: http://www.openlinksw.com/blog/~kidehen/ http://kidehen.blogspot.com Profile Pages: Pinterest: https://www.pinterest.com/kidehen/ Quora: https://www.quora.com/profile/Kingsley-Uyi-Idehen Twitter: https://twitter.com/kidehen Google+: https://plus.google.com/+KingsleyIdehen/about LinkedIn: http://www.linkedin.com/in/kidehen Web Identities (WebID): Personal: http://kingsley.idehen.net/public_home/kidehen/profile.ttl#i : http://id.myopenlink.net/DAV/home/KingsleyUyiIdehen/Public/kingsley.ttl#this _______________________________________________ Wikidata mailing list Wikidata@lists.wikimedia.org <mailto:Wikidata@lists.wikimedia.org> https://lists.wikimedia.org/mailman/listinfo/wikidata
Wikidata mailing list Wikidata@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata
Hi!
Le mer. 14 août 2019 à 01:10, Kingsley Idehen kidehen@openlinksw.com a écrit :
We have loaded Wikidata into a Virtuoso instance accessible via SPARQL [1]. One benefit is helping to understand Wikidata using our Faceted Browsing Interface for Entity Relationship Types [2][3].
That's great news, thanks!
Feedback always welcome too :)
So, I've eagerly tried a very simple SPARQL query with a huge result set, the complete version of which¹ I've known for several years to timeout in both the official Blazegraph instance and a personal Blazegraph instance with supposedly all time limits removed:
PREFIX wd: http://www.wikidata.org/entity/ PREFIX wdt: http://www.wikidata.org/prop/direct/
SELECT ?person WHERE { ?person wdt:P31 wd:Q5 }
… and while the Virtuoso instance manages to answer pretty quickly, it seems that it's cutting the result set at 100k triples. Is it the expected behavior? If so, I suggest you show that in the UI because apart from the improbable round number of triples, it's not obvious that the result set is incomplete (in this case, the LDF endpoint tells us that there should be around 5,4M triples²).
Thanks again!
¹ ie. using the wikibase:label service ² https://query.wikidata.org/bigdata/ldf?subject=&predicate=wdt%3AP31&...
On 8/14/19 6:07 AM, Jérémie Roquet wrote:
Hi!
Le mer. 14 août 2019 à 01:10, Kingsley Idehen kidehen@openlinksw.com a écrit :
We have loaded Wikidata into a Virtuoso instance accessible via SPARQL [1]. One benefit is helping to understand Wikidata using our Faceted Browsing Interface for Entity Relationship Types [2][3].
That's great news, thanks!
Hi Jérémie,
You are welcome! See responses below.
Feedback always welcome too :)
So, I've eagerly tried a very simple SPARQL query with a huge result set, the complete version of which¹ I've known for several years to timeout in both the official Blazegraph instance and a personal Blazegraph instance with supposedly all time limits removed:
PREFIX wd: http://www.wikidata.org/entity/ PREFIX wdt: http://www.wikidata.org/prop/direct/
SELECT ?person WHERE { ?person wdt:P31 wd:Q5 }
… and while the Virtuoso instance manages to answer pretty quickly, it seems that it's cutting the result set at 100k triples. Is it the expected behavior?
Yes.
If so, I suggest you show that in the UI because apart from the improbable round number of triples, it's not obvious that the result set is incomplete (in this case, the LDF endpoint tells us that there should be around 5,4M triples²).
Thanks again!
¹ ie. using the wikibase:label service ² https://query.wikidata.org/bigdata/ldf?subject=&predicate=wdt%3AP31&...
If you open up your browser's inspector you will see:
cache-control: max-age=3600 content-encoding: gzip content-type: text/html; charset=UTF-8 date: Wed, 14 Aug 2019 16:47:47 GMT expires: Wed, 14 Aug 2019 17:47:47 GMT server: Virtuoso/08.03.3315 (Linux) x86_64-generic-linux-glibc25 VDB status: 200 strict-transport-security: max-age=15768000 vary: Accept-Encoding x-sparql-default-graph: http://www.wikidata.org/ *x-sparql-maxrows:* 100000
In addition, note that Virtuoso has an "Anytime Query" feature [1][2] that it uses to drive a "Fair Use" policy that ensures an endpoint is able to handle a cocktail of query types from users and bots. This is also how we handle DBpedia and DBpedia-Live instances [3]. Naturally, HTTP response metadata will also inform you when this kicks in.
[1] http://docs.openlinksw.com/virtuoso/anytimequeries/
[2] http://vos.openlinksw.com/owiki/wiki/VOS/VirtTipsAndTricksAnytimeSPARQLQuery
[3] https://wiki.dbpedia.org/public-sparql-endpoint
On Wed, Aug 14, 2019 at 1:10 AM Kingsley Idehen kidehen@openlinksw.com wrote:
We have loaded Wikidata into a Virtuoso instance accessible via SPARQL [1]. One benefit is helping to understand Wikidata using our Faceted Browsing Interface for Entity Relationship Types [2][3].
Awesome!
I've started seeing how much of Scholia can run on it, and opened a ticket: https://github.com/fnielsen/scholia/issues/809 It's great the Wikidata namespaces are loaded. I only had to add the 'bd' prefix to the Scholia SPARQL. And, the sections that use the WDQS graphical views, obviously cannot use the VOS instance yet.
So, do you plan to run a WDQS instance on top of your EP? :)
Egon
On 8/14/19 4:35 PM, Egon Willighagen wrote:
On Wed, Aug 14, 2019 at 1:10 AM Kingsley Idehen kidehen@openlinksw.com wrote:
We have loaded Wikidata into a Virtuoso instance accessible via SPARQL [1]. One benefit is helping to understand Wikidata using our Faceted Browsing Interface for Entity Relationship Types [2][3].
Awesome!
I've started seeing how much of Scholia can run on it, and opened a ticket: https://github.com/fnielsen/scholia/issues/809 It's great the Wikidata namespaces are loaded. I only had to add the 'bd' prefix to the Scholia SPARQL. And, the sections that use the WDQS graphical views, obviously cannot use the VOS instance yet.
So, do you plan to run a WDQS instance on top of your EP? :)
Egon
I am hoping that WDQS would be encouraged to be more loosely-coupled based on SPARQL as the open standard for its data access etc..
There are lots of tools from this community that will benefit immensely from loose-coupling, IMHO.
We need to demonstrate to the world that the LOD Cloud is its most powerful and accessible Knowledge Graph :)
Thanks for this, Kingsley.
Based on https://docs.google.com/spreadsheets/d/1-stlTC_WJmMU3xA_NxA1tSLHw6_sbpjff-5O... (copy-pasted below), it seems that it takes 43 hours to load, is that correct?
Also, what is the "patch for geometry" mentioned there? I'm assuming that is the patch meant to address https://github.com/openlink/virtuoso-opensource/issues/295 and https://community.openlinksw.com/t/non-terrestrial-geo-literals/359, correct? Is it simply disabling the data validation code? Can you share the patch?
Thanks, Edgar
Other Information Architecture x86_64 CPU op-mode(s) 32-bit, 64-bit Byte Order Little Endian CPU(s) 12.00 On-line CPU(s) list 0-11 Thread(s) per core 2.00 Core(s) per socket 6.00 Socket(s) 1.00 NUMA node(s) 1.00 Vendor ID GenuineIntel CPU family 6.00 Model 63.00 Model name Intel(R) Xeon(R) CPU E5-1650 v3 @ 3.50GHz Stepping 2.00 CPU MHz 1,199.92 CPU max MHz 3,800.00 CPU min MHz 1,200.00 BogoMIPS 6,984.39 Virtualization VT-x L1d cache 32K L1i cache 32K L2 cache 256K L3 cache 15360K NUMA node0 CPU(s) 0-11 RAM 128G wikidata-20190610-all-BETA.ttl 383G Virtuoso version 07.20.3230 (with patch for geometry) Time to load 43 hours virtuoso.db 340G
On Wed, Aug 14, 2019 at 12:10 AM Kingsley Idehen kidehen@openlinksw.com wrote:
Hi Everyone,
A little FYI.
We have loaded Wikidata into a Virtuoso instance accessible via SPARQL [1]. One benefit is helping to understand Wikidata using our Faceted Browsing Interface for Entity Relationship Types [2][3].
Links:
[1] http://wikidata.demo.openlinksw.com/sparql -- SPARQL endpoint
[2] http://wikidata.demo.openlinksw.com/fct -- Faceted Browsing Interface
[3] About New York https://wikidata.demo.openlinksw.com/describe/?url=http%3A%2F%2Fwww.wikidata.org%2Fentity%2FQ60&gp=16&go=&lp=940&invfp=IFP_OFF&sas=SAME_AS_OFF&distinct=1
Enjoy!
Feedback always welcome too :)
-- Regards,
Kingsley Idehen Founder & CEO OpenLink Software Home Page: http://www.openlinksw.com Community Support: https://community.openlinksw.com Weblogs (Blogs): Company Blog: https://medium.com/openlink-software-blog Virtuoso Blog: https://medium.com/virtuoso-blog Data Access Drivers Blog: https://medium.com/openlink-odbc-jdbc-ado-net-data-access-drivers
Personal Weblogs (Blogs): Medium Blog: https://medium.com/@kidehen Legacy Blogs: http://www.openlinksw.com/blog/~kidehen/ http://kidehen.blogspot.com
Profile Pages: Pinterest: https://www.pinterest.com/kidehen/ Quora: https://www.quora.com/profile/Kingsley-Uyi-Idehen Twitter: https://twitter.com/kidehen Google+: https://plus.google.com/+KingsleyIdehen/about LinkedIn: http://www.linkedin.com/in/kidehen
Web Identities (WebID): Personal: http://kingsley.idehen.net/public_home/kidehen/profile.ttl#i : http://id.myopenlink.net/DAV/home/KingsleyUyiIdehen/Public/kingsley.ttl#this
Wikidata mailing list Wikidata@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata
On 9/1/19 5:14 AM, Edgar Meij wrote:
Thanks for this, Kingsley.
Based on https://docs.google.com/spreadsheets/d/1-stlTC_WJmMU3xA_NxA1tSLHw6_sbpjff-5O... (copy-pasted below), it seems that it takes 43 hours to load, is that correct?
Yes, for that particular single-server instance configuration.
Also, what is the "patch for geometry" mentioned there? I'm assuming that is the patch meant to address https://github.com/openlink/virtuoso-opensource/issues/295 and https://community.openlinksw.com/t/non-terrestrial-geo-literals/359, correct? Is it simply disabling the data validation code? Can you share the patch?
Best we move this particular item to our community forum [1].
Links:
[1] https://community.openlinksw.com
Kingsley
Thanks, Edgar
Other Information
Architecture x86_64 CPU op-mode(s) 32-bit, 64-bit Byte Order Little Endian CPU(s) 12.00 On-line CPU(s) list 0-11 Thread(s) per core 2.00 Core(s) per socket 6.00 Socket(s) 1.00 NUMA node(s) 1.00 Vendor ID GenuineIntel CPU family 6.00 Model 63.00 Model name
Intel(R) Xeon(R) CPU E5-1650 v3 @ 3.50GHz Stepping 2.00 CPU MHz 1,199.92 CPU max MHz 3,800.00 CPU min MHz 1,200.00 BogoMIPS 6,984.39 Virtualization VT-x L1d cache 32K L1i cache 32K L2 cache 256K L3 cache 15360K NUMA node0 CPU(s) 0-11 RAM 128G
wikidata-20190610-all-BETA.ttl 383G Virtuoso version
07.20.3230 (with patch for geometry) Time to load 43 hours virtuoso.db 340G
On Wed, Aug 14, 2019 at 12:10 AM Kingsley Idehen <kidehen@openlinksw.com mailto:kidehen@openlinksw.com> wrote:
Hi Everyone, A little FYI. We have loaded Wikidata into a Virtuoso instance accessible via SPARQL [1]. One benefit is helping to understand Wikidata using our Faceted Browsing Interface for Entity Relationship Types [2][3]. Links: [1] http://wikidata.demo.openlinksw.com/sparql -- SPARQL endpoint [2] http://wikidata.demo.openlinksw.com/fct -- Faceted Browsing Interface [3] About New York <https://wikidata.demo.openlinksw.com/describe/?url=http%3A%2F%2Fwww.wikidata.org%2Fentity%2FQ60&gp=16&go=&lp=940&invfp=IFP_OFF&sas=SAME_AS_OFF&distinct=1> Enjoy! Feedback always welcome too :) -- Regards, Kingsley Idehen Founder & CEO OpenLink Software Home Page: http://www.openlinksw.com Community Support: https://community.openlinksw.com Weblogs (Blogs): Company Blog: https://medium.com/openlink-software-blog Virtuoso Blog: https://medium.com/virtuoso-blog Data Access Drivers Blog: https://medium.com/openlink-odbc-jdbc-ado-net-data-access-drivers Personal Weblogs (Blogs): Medium Blog: https://medium.com/@kidehen Legacy Blogs: http://www.openlinksw.com/blog/~kidehen/ http://kidehen.blogspot.com Profile Pages: Pinterest: https://www.pinterest.com/kidehen/ Quora: https://www.quora.com/profile/Kingsley-Uyi-Idehen Twitter: https://twitter.com/kidehen Google+: https://plus.google.com/+KingsleyIdehen/about LinkedIn: http://www.linkedin.com/in/kidehen Web Identities (WebID): Personal: http://kingsley.idehen.net/public_home/kidehen/profile.ttl#i : http://id.myopenlink.net/DAV/home/KingsleyUyiIdehen/Public/kingsley.ttl#this _______________________________________________ Wikidata mailing list Wikidata@lists.wikimedia.org <mailto:Wikidata@lists.wikimedia.org> https://lists.wikimedia.org/mailman/listinfo/wikidata
Wikidata mailing list Wikidata@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata
Hi
I was able to reduce the load time to 9.1 hours aprox. (32890338 msec) in Virtuoso 7. I used 6 SSD disks of 1T each with RAID 0 (mdadm software RAID, I have not tried with hardware RAID). The virtuoso.ini for 256G RAM is https://gist.github.com/asanchez75/58d5aed504051c7fbf9af0921c3c9130 I downloaded the dump from https://dumps.wikimedia.org/wikidatawiki/entities/latest-all.ttl.gz on August 30th, The size is 387G uncompressed and finally the file virtuoso.db is 362G. The total number of triples is 9 470 700 617. Have a look to the simple patch here (is just a workaround) https://github.com/asanchez75/virtuoso-opensource/commit/5d7b1b9b29e53cb8a25... You can create your own docker image with that patch using https://github.com/asanchez75/docker-virtuoso/tree/brendan Check the Dockerfile which retrieves the patch from my forked Virtuoso git repository https://github.com/asanchez75/docker-virtuoso/blob/brendan/Dockerfile
Best,
Le dim. 1 sept. 2019 à 13:38, Edgar Meij edgar.meij@gmail.com a écrit :
Thanks for this, Kingsley.
Based on https://docs.google.com/spreadsheets/d/1-stlTC_WJmMU3xA_NxA1tSLHw6_sbpjff-5O... (copy-pasted below), it seems that it takes 43 hours to load, is that correct?
Also, what is the "patch for geometry" mentioned there? I'm assuming that is the patch meant to address https://github.com/openlink/virtuoso-opensource/issues/295 and https://community.openlinksw.com/t/non-terrestrial-geo-literals/359, correct? Is it simply disabling the data validation code? Can you share the patch?
Thanks, Edgar
Other Information Architecture x86_64 CPU op-mode(s) 32-bit, 64-bit Byte Order Little Endian CPU(s) 12.00 On-line CPU(s) list 0-11 Thread(s) per core 2.00 Core(s) per socket 6.00 Socket(s) 1.00 NUMA node(s) 1.00 Vendor ID GenuineIntel CPU family 6.00 Model 63.00 Model name Intel(R) Xeon(R) CPU E5-1650 v3 @ 3.50GHz Stepping 2.00 CPU MHz 1,199.92 CPU max MHz 3,800.00 CPU min MHz 1,200.00 BogoMIPS 6,984.39 Virtualization VT-x L1d cache 32K L1i cache 32K L2 cache 256K L3 cache 15360K NUMA node0 CPU(s) 0-11 RAM 128G wikidata-20190610-all-BETA.ttl 383G Virtuoso version 07.20.3230 (with patch for geometry) Time to load 43 hours virtuoso.db 340G
On Wed, Aug 14, 2019 at 12:10 AM Kingsley Idehen kidehen@openlinksw.com wrote:
Hi Everyone,
A little FYI.
We have loaded Wikidata into a Virtuoso instance accessible via SPARQL [1]. One benefit is helping to understand Wikidata using our Faceted Browsing Interface for Entity Relationship Types [2][3].
Links:
[1] http://wikidata.demo.openlinksw.com/sparql -- SPARQL endpoint
[2] http://wikidata.demo.openlinksw.com/fct -- Faceted Browsing Interface
[3] About New York https://wikidata.demo.openlinksw.com/describe/?url=http%3A%2F%2Fwww.wikidata.org%2Fentity%2FQ60&gp=16&go=&lp=940&invfp=IFP_OFF&sas=SAME_AS_OFF&distinct=1
Enjoy!
Feedback always welcome too :)
-- Regards,
Kingsley Idehen Founder & CEO OpenLink Software Home Page: http://www.openlinksw.com Community Support: https://community.openlinksw.com Weblogs (Blogs): Company Blog: https://medium.com/openlink-software-blog Virtuoso Blog: https://medium.com/virtuoso-blog Data Access Drivers Blog: https://medium.com/openlink-odbc-jdbc-ado-net-data-access-drivers
Personal Weblogs (Blogs): Medium Blog: https://medium.com/@kidehen Legacy Blogs: http://www.openlinksw.com/blog/~kidehen/ http://kidehen.blogspot.com
Profile Pages: Pinterest: https://www.pinterest.com/kidehen/ Quora: https://www.quora.com/profile/Kingsley-Uyi-Idehen Twitter: https://twitter.com/kidehen Google+: https://plus.google.com/+KingsleyIdehen/about LinkedIn: http://www.linkedin.com/in/kidehen
Web Identities (WebID): Personal: http://kingsley.idehen.net/public_home/kidehen/profile.ttl#i : http://id.myopenlink.net/DAV/home/KingsleyUyiIdehen/Public/kingsley.ttl#this
Wikidata mailing list Wikidata@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata
Wikidata mailing list Wikidata@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata
On 9/2/19 3:51 PM, Adam Sanchez wrote:
Hi
I was able to reduce the load time to 9.1 hours aprox. (32890338 msec) in Virtuoso 7. I used 6 SSD disks of 1T each with RAID 0 (mdadm software RAID, I have not tried with hardware RAID). The virtuoso.ini for 256G RAM is https://gist.github.com/asanchez75/58d5aed504051c7fbf9af0921c3c9130 I downloaded the dump from https://dumps.wikimedia.org/wikidatawiki/entities/latest-all.ttl.gz%C2%A0 on August 30th, The size is 387G uncompressed and finally the file virtuoso.db is 362G. The total number of triples is 9 470 700 617. Have a look to the simple patch here (is just a workaround) https://github.com/asanchez75/virtuoso-opensource/commit/5d7b1b9b29e53cb8a25... You can create your own docker image with that patch using https://github.com/asanchez75/docker-virtuoso/tree/brendan Check the Dockerfile which retrieves the patch from my forked Virtuoso git repository https://github.com/asanchez75/docker-virtuoso/blob/brendan/Dockerfile
Best,
Great job!
I've granted access to you via your email address so that you can update the Google Spreadsheet containing configuration details per sample Virtuoso instances [1]. You can put your data in the Wikidata worksheet [2].
Links:
[1] https://docs.google.com/spreadsheets/d/1-stlTC_WJmMU3xA_NxA1tSLHw6_sbpjff-5O...
[2] https://docs.google.com/spreadsheets/d/1-stlTC_WJmMU3xA_NxA1tSLHw6_sbpjff-5O...
Kingsley
Le dim. 1 sept. 2019 à 13:38, Edgar Meij <edgar.meij@gmail.com mailto:edgar.meij@gmail.com> a écrit :
Thanks for this, Kingsley. Based on https://docs.google.com/spreadsheets/d/1-stlTC_WJmMU3xA_NxA1tSLHw6_sbpjff-5OITtrbFw/edit#gid=1799898600 (copy-pasted below), it seems that it takes 43 hours to load, is that correct? Also, what is the "patch for geometry" mentioned there? I'm assuming that is the patch meant to address https://github.com/openlink/virtuoso-opensource/issues/295 and https://community.openlinksw.com/t/non-terrestrial-geo-literals/359, correct? Is it simply disabling the data validation code? Can you share the patch? Thanks, Edgar Other Information Architecture x86_64 CPU op-mode(s) 32-bit, 64-bit Byte Order Little Endian CPU(s) 12.00 On-line CPU(s) list 0-11 Thread(s) per core 2.00 Core(s) per socket 6.00 Socket(s) 1.00 NUMA node(s) 1.00 Vendor ID GenuineIntel CPU family 6.00 Model 63.00 Model name Intel(R) Xeon(R) CPU E5-1650 v3 @ 3.50GHz Stepping 2.00 CPU MHz 1,199.92 CPU max MHz 3,800.00 CPU min MHz 1,200.00 BogoMIPS 6,984.39 Virtualization VT-x L1d cache 32K L1i cache 32K L2 cache 256K L3 cache 15360K NUMA node0 CPU(s) 0-11 RAM 128G wikidata-20190610-all-BETA.ttl 383G Virtuoso version 07.20.3230 (with patch for geometry) Time to load 43 hours virtuoso.db 340G On Wed, Aug 14, 2019 at 12:10 AM Kingsley Idehen <kidehen@openlinksw.com <mailto:kidehen@openlinksw.com>> wrote: Hi Everyone, A little FYI. We have loaded Wikidata into a Virtuoso instance accessible via SPARQL [1]. One benefit is helping to understand Wikidata using our Faceted Browsing Interface for Entity Relationship Types [2][3]. Links: [1] http://wikidata.demo.openlinksw.com/sparql -- SPARQL endpoint [2] http://wikidata.demo.openlinksw.com/fct -- Faceted Browsing Interface [3] About New York <https://wikidata.demo.openlinksw.com/describe/?url=http%3A%2F%2Fwww.wikidata.org%2Fentity%2FQ60&gp=16&go=&lp=940&invfp=IFP_OFF&sas=SAME_AS_OFF&distinct=1> Enjoy! Feedback always welcome too :) -- Regards, Kingsley Idehen Founder & CEO OpenLink Software Home Page: http://www.openlinksw.com Community Support: https://community.openlinksw.com Weblogs (Blogs): Company Blog: https://medium.com/openlink-software-blog Virtuoso Blog: https://medium.com/virtuoso-blog Data Access Drivers Blog: https://medium.com/openlink-odbc-jdbc-ado-net-data-access-drivers Personal Weblogs (Blogs): Medium Blog: https://medium.com/@kidehen Legacy Blogs: http://www.openlinksw.com/blog/~kidehen/ http://kidehen.blogspot.com Profile Pages: Pinterest: https://www.pinterest.com/kidehen/ Quora: https://www.quora.com/profile/Kingsley-Uyi-Idehen Twitter: https://twitter.com/kidehen Google+: https://plus.google.com/+KingsleyIdehen/about LinkedIn: http://www.linkedin.com/in/kidehen Web Identities (WebID): Personal: http://kingsley.idehen.net/public_home/kidehen/profile.ttl#i : http://id.myopenlink.net/DAV/home/KingsleyUyiIdehen/Public/kingsley.ttl#this _______________________________________________ Wikidata mailing list Wikidata@lists.wikimedia.org <mailto:Wikidata@lists.wikimedia.org> https://lists.wikimedia.org/mailman/listinfo/wikidata _______________________________________________ Wikidata mailing list Wikidata@lists.wikimedia.org <mailto:Wikidata@lists.wikimedia.org> https://lists.wikimedia.org/mailman/listinfo/wikidata
Wikidata mailing list Wikidata@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata