Hi Sebastian,
Can you apply the attached patch to your libsrc/Wi directory and try
again please. This should make your insert run in much better
time, even
without large number of buffers.
Impressive. Even with 5000 buffers it only takes 3 seconds or less
(I timed
everything including st
HI Sebastian,
Looking at the Virtuoso configuration file params you provided I
not you
are running in LiteMode, with only the following set:
[Parameters]
LiteMode=1
ServerPort=
DisableTcpSocket=1
PrefixResultNames=0
ServerThreads=5
CheckpointInterval=10
MaxDirtyBuffers=50
SchedulerInterva
Hugh Williams wrote:
> Looking at the Virtuoso configuration file params you provided I not you
> are running in LiteMode, with only the following set:
>
>> [Parameters]
>> LiteMode=1
>> ServerPort=
>> DisableTcpSocket=1
>> PrefixResultNames=0
>> ServerThreads=5
>> CheckpointInterval=10
>> M
Hi Sebastian,
Looking at the Virtuoso configuration file params you provided I not
you are running in LiteMode, with only the following set:
[Parameters]
LiteMode=1
ServerPort=
DisableTcpSocket=1
PrefixResultNames=0
ServerThreads=5
CheckpointInterval=10
MaxDirtyBuffers=50
SchedulerInterv
I cannot give you the odbc.log from the original situation. That file is
more than 1GB in size.
But I recreated the situation with some dummy data using an empty
database which I started with the attached config file. This time the
query even shows up in the iodbc.log file.
The virtuoso log is empt
Hi Sebastian,
Can you please provide a complete iODBC trace so we can see the query
and sequence of call be made. It might also we worth checking the
Virtuoso Server log (virtuoso.log) to see if any errors are being
reported on that side.
Best Regards
Hugh Williams
Professional Services
O
I have a problem with adding very large literal objects to Virtuoso. In
fact, Virtuoso sat there during the whole night using nearly all CPU and
not finishing the insert query.
In the log it looks something like this:
[06.264449]
nepomukservices 7F1307359950 ENTER SQLExecDirect
