I don't think that is true. SQLite seems to divide its database file into pages. See these comments here:

No. SQLite uses the B-Tree algorithm. Inserting a new value in the middle of a table involves rewriting 4 or 5 pages in the worst case. The usual case is to rewrite just the one page where the value is being inserted.

and here in the SQLite optimization FAQ:

An SQLite database is split into a btree of "pages" which are 1K in size by default

One thing to speed up inserts seems to be using transactions to group a batch of writes

While SQLite is probably better used for smaller projects, the definition of small is somewhat debatable. I assume that mysql and postgres have a lot more optimizations in place for complicated queries with joins etc. Also separating the database from the client means you can utilize at least a separate database server or through replication even more to split the load. But performance for simple sql queries on one machine seems to be comparable to the bigger engines (if you believe the SQLite makers). Also see this comment:

I'd have to differ on opinion here. I have an sqlite database that's at 6.9GB with about 40 million records, and it's working just fine.

In reply to Re^2: Which one is faster ? by jethro
in thread OT : Which one is faster ? by vinoth.ree

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.