Yuck...do you know what bandwidth you have? Looks kind of like a T1 line to me.
That should allow 100Meg to come across in about 13 minutes if it's not being
used for anything else. Unless you're monitoring time usage in your
application how do you know where your time is being spent? If the T1 line is
busy that will slow you down more and if you're not measuring both Oracle and
Sqlite time independently how do you know??
I would optimize your local write first to see what the optimum transaction
size is and other options you can set. Then use those options on your network
write.
And have you considered trying 3.7.0 and use WAL? Seems like your application
might benefit quite a bit from that.
You could also split your app in 2 (this would work witih CLAR too). Have your
Oracle app write to a named pipe and your CLAR/SQlite read the data from the
name pipe. Then your Oracle app can trot off to retrieve another record whild
your DB app writes to your database. This is a pretty simple way to do
multitasking without writing code and would get rid of some your latency.
I assume you've got a test data file with all your SQL statements in it that
you can test with? That's the best way to optimize your local database writing
options.
Michael D. Black
Senior Scientist
Northrop Grumman Mission Systems
________________________________
From: sqlite-users-boun...@sqlite.org on behalf of Werner Smit
Sent: Wed 7/14/2010 11:43 AM
To: General Discussion of SQLite Database
Subject: EXTERNAL:Re: [sqlite] Sqlite Insert Speed Optimization
If you don't know why it's slow you'll be shooting in the dark. And
doing compression on a local network link isn't likely to buy you much.
Might even hurt.
In other words, is it latency or bandwidth? Give 8K/sec I'm guessing
it's latency unless you're running a 64KBit line. Are you THAT slow???
What's your ping time latency look like?
________________________________
Ping Latency :
Pinging allpay [196.11.183.3] with 32 bytes of data:
Reply from 196.11.183.3: bytes=32 time=115ms TTL=250
Reply from 196.11.183.3: bytes=32 time=175ms TTL=250
..
Reply from 196.11.183.3: bytes=32 time=228ms TTL=250
Reply from 196.11.183.3: bytes=32 time=264ms TTL=250
Ping statistics for 196.11.183.3:
Packets: Sent = 8, Received = 8, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 74ms, Maximum = 264ms, Average = 178ms
DISCLAIMER:
Everything in this email and its attachments relating to the official business
of Face Technologies is proprietary to Face Technologies. It is confidential,
legally privileged and protected by law. The person addressed in the email is
the sole authorised recipient. Any unauthorized dissemination or copying of
this e-mail (or any attachment to this e-mail) or the wrongful disclosure of
the information herein contained is prohibited.
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
