Open maxpoulain opened 3 years ago
@maxpoulain Did you resolve the issue? I have the same issue.
No I did not solve the problem.
@Tpt Do you have the same error/bug ?
I ran into the same or very similar issue. The yago4 process consumes the whole available memory (in my case 128Gb) and exits quietly. The error could be found only in the /var/log/syslog in Ubuntu - the message is something like this: yago4 invoked oom-killer: gfp_mask=0x100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0
@maxpoulain , @Vikas-Jethwani, could you guys confirm that you are experiencing the same problem or it is another issue?
@Tpt could you please share the configuration (RAM, CPU. OS) used to generate Yago4?
Hi,
I have a new question/issue regarding the code of yago4.
I ran the code on the latest wikipedia dump following the README and I have a problem when I ran
cargo run --release -- -c wd-preprocessed.db build -o yago4 --full
:It's writing files but the code never ends and does not write the stats file, It seems stuck.. and we can let it run for hours it doesn't change a thing but there is no error.. And also when I look at the size of the files some are much smaller than those present here as you can see:
In fact, it's our
yago-wd-facts.nt.gz
andyago-wd-annotated-facts.ntx.gz
that are really really smaller than expected.On the first step of Yago
cargo run --release -- -c wd-preprocessed.db partition -f latest-all.nt.gz
I have preprocessed.db that is around 422 Go, so I think that is good.Here are the logs I have:
So, I know that I don't have a lot of elements to find where is the problem but I would like to understand, if I'm doing something wrong or if there is a bug or an error somewhere..
Thanks for your help.
Maxime