I'm using sqlite as an embedded engine in the application acting like server for other applications.
Pavel On Sun, Apr 26, 2009 at 4:17 PM, John Stanton <jo...@viacognis.com> wrote: > Sqlite does not use a server. It is embedded in the application. > > Pavel Ivanov wrote: >> Unfortunately these two options are not for me. >> I'm not in control of servers hardware, so my application should work >> on the given servers and nobody will adjust them for my application. >> And about first option, I believe what you say is to use in-memory >> database for intensive operations. But all my application consists of >> these intensive operations alone. So that you can reasonably argue >> that I should reject the idea of on-disk database and work totally in >> memory. And i can agree with you. But there's a couple of requirements >> that make things difficult. And the main of it is application should >> have some durability and survive power outages, crashes and reboots. >> "Some" because I can sacrifice for example everything that was written >> up to 5 minutes before power outage, but everything else should stay. >> And at this point all idea of in-memory database is ruined and I have >> to cope somehow with problems of frequent writings to disk. >> >> >> Pavel >> >> On Fri, Apr 24, 2009 at 6:13 AM, January Weiner <janu...@uni-muenster.de> >> wrote: >> >>>> I have an application written using sqlite. It writes into the >>>> database very intensively. And I noticed that it works nice and very >>>> fast but from time to time it just freezes for several seconds (I've >>>> registered freezes up to 8 secs). After some tracing of sqlite code >>>> >>> I had the same problem. Also, it was increasing with database size. >>> Depending on your environment, work procedure and whether you want >>> speed or security, there are two things that work beautifully for me: >>> >>> 1) do the intentsive work on a db copy that sits on a ramdisk (or >>> tmpfs filesystem). I do that if I have to create a new database or >>> rebuild this from scratch, and since the process is supervised, there >>> is not really a danger of data loss. >>> >>> 2) for normal operation, I use a software RAID from flash disks, which >>> is not as fast (for data transfer) as a hard drive or SSD, but it is >>> has a response time better by an order of magnitude (at least) than >>> even a good hard drive. >>> >>> j. >>> >>> -- >>> ---------Dr. January Weiner 3 -----------------+------------------- >>> Inst. of Bioinformatics, UKM, Univ. of Muenster | Von-Esmarch-str. 54 >>> (+49) (251) 83 53002 | D48149 Münster >>> http://www.compgen.uni-muenster.de/ | Germany >>> _______________________________________________ >>> 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 >> > > _______________________________________________ > 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
