Difference between revisions of "Wikidata on Allegrograph"
Jump to navigation
Jump to search
(2 intermediate revisions by the same user not shown) | |||
Line 6: | Line 6: | ||
|target=Allegrograph | |target=Allegrograph | ||
|start=2022-04-15 | |start=2022-04-15 | ||
− | |days=0 | + | |days=0.3 |
|os=CentOS Linux release 7.9.2009 | |os=CentOS Linux release 7.9.2009 | ||
+ | |cpu=AMD EPYC 7302, 3.0GHz | ||
|ram=256 | |ram=256 | ||
− | |triples= | + | |triples=16.8 |
}} | }} | ||
=Freitext= | =Freitext= |
Latest revision as of 08:24, 16 May 2023
Import
Import | |
---|---|
state | ✅ |
url | https://wiki.bitplan.com/index.php/Wikidata_on_Allegrograph |
target | Allegrograph |
start | 2022-04-15 |
end | |
days | 0.3 |
os | CentOS Linux release 7.9.2009 |
cpu | AMD EPYC 7302, 3.0GHz |
ram | 256 |
triples | 16.8 |
comment |
Freitext
Craig Norvell wrote on 2022-07-25:
We loaded https://dumps.wikimedia.org/wikidatawiki/entities/latest-all.nt.gz (Probably from mid-April 2022 time frame) Machine - 32core (2x16 AMD EPYC 7302, 3.0GHz), 256GB RAM, CentOS Linux release 7.9.2009 with SSDs. Load using only 16 cores took <6 hours. Triple count - 16,882,554,798 Size on Disk - 1,486GB For faster queries we optimized the indices (Oscore to 1.0) and that took <6 hours. 74% of the queries took <100 milliseconds. 98.5% finished in <1sec There was a single query that took 7.19 seconds and we might have a look to see if adding an index might change that result. We have not investigated different hardware configs (<RAM, Spinning Disks, <Cores, etc).