to close this subject I have some more information.
After a try on my ubuntu I notice that the différence doesn't exist. So I
ugraded the production HOST to à 4.4 linux kernel.
The timing is now the same on the host and in the container ( but both are
slower. snif ... )
fs tuning is not so
Perhaps the file sync performed by SQLite is more expensive in the docker
environment than in the host. That would make sense to me.
On Nov 30, 2017 7:07 AM, "Sebastien HEITZMANN" <2...@2le.net> wrote:
> In my last mail i have multiple table creation and index. It seam that the
> overtime is for
In my last mail i have multiple table creation and index. It seam that the
overtime is for all the create statement.
It really looks like a disk pb. But can't identify so much difference in my
direct disk access ( with DD )
I will try it on an other host.
2017-11-30 14:59 GMT+01:00 Simon Slavin
OP wrote:
> CREATE TABLE f (fid VARCHAR, path VARCHAR, meta VARCHAR, mtime INTEGER,
> virtual INTEGER, pfid VARCHAR, type VARCHAR, ts INTEGER);
Is this the first content of a new file ? If so, SQLite has to create the file
and write some structure information as well as writing the table. I
my test script is a little bit more complicated but with .timer it give
this result. Each statement is longer. So no load time or something like
that.
ON HOST
root@dipsy:/usr/share/kserver4# time sqlite3 dbm.db < dbm.sql
Run Time: real 0.027 user 0.00 sys 0.00
Run Time: real 0.020 user
All my other tests give me some equivalent time in host and in container.
I have reduced the problem to the creation of the database. The rest of my
workload run approximatively in the same time.
You're right, there is some variance between each test but the 4 factor
stay the same. Sometime it's
In addition to the execution time of the SQL you are also measuring time to
load and link the sqlite3 command.
A perhaps more realistic test would be to change the f.sql to contain:
.timer on
CREATE TABLE f (fid VARCHAR, path VARCHAR, meta VARCHAR, mtime INTEGER,
virtual INTEGER, pfid
> Le 30 nov. 2017 à 12:00, Sebastien HEITZMANN <2...@2le.net> a écrit :
>
> We juste create a sigle table in a new db. In my docker container it take 4
> time more time than in the host system.
>
> time sqlite3 /tmp/foo.db < f.sql
>
> on the host machine
> real 0m0.216s
>
> and in the docker
8 matches
Mail list logo
