-
Notifications
You must be signed in to change notification settings - Fork 214
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not able to load large Turtle files in V7 #40
Comments
please try using |
OK, tried |
What dataset are you trying to load? Can you provide a link to it so we can do an in-house test on this? |
Tried again today with version
|
Development is currently setting up a test with your data inhouse in order to debug this issue. |
Can you try setting
As this has resolved slow load rate to the point of hanging for other users... |
OK, tried this setting. The load eventually finished, but took a long time and still there were these messages in the log:
|
these messages can be neglected unless other issue at same time. |
This time Virtuoso did not crash, there were peaks of both CPU activity and IO activity alternating with nothing happening in approx. 20 seconds intervals - 20 s of activity, 5-10s of nothing. |
this issue has been fixed in |
Tried latest develop/7 commit 3fed005 and it still hangs. The log contains:
|
Still happening in 7.0.1. d9af7aa |
Has not happened for a long time, can be closed? |
Having the same issue trying to load DBpedia. I'm using newest develop/7
|
Have you attempted the crash dump and restore as suggested? Which Dbpedia dataset(s) was being loaded when the error occurred? |
I solved my problem. There were spaces before now that buffer size is |
Not happening anymore |
Virtuoso 7
commit a9356b9c8a52d5ce7ac1864df922ce46c67acd2f
(April 25)When loading large files (2GB) using
DB.DBA.TTLP_MT (file_to_string_output ('filename'), '', 'graphname');
virtuoso eventually either hangs (CPU usage 100% for a looong time but nothing happens) or it says
Transaction deadlocked
.In virtuoso.ini:
the machine has 8GB of RAM.
In the log:
The text was updated successfully, but these errors were encountered: