OT: Wikis

[Ruslan Zasukhin]

On 10/18/05 10:06 PM, "chris bohnert" <chris at altuit.com> wrote:

Hi Chris,

> To me, this is the definition of a professional enterprise tool;

Oh man. Even mySQL is VERY careful to TRY name self enterprise tool,
As well as Postgre SQL.

Sql Lite exactly even do not touch and is not going touch that level.

> something I can use in an extremely heterogenous envirnoment to perform
> a task or solve a problem without fear that I've locked my customer into
> the migrational whims of a single vendor.

Again, SqlLite is good until your Application that embed it, play with db of
size 1-50MB. Or do some very simple queries.

I am not going start now discussion of technical problems of SqlLite, but
they are quite visible.

Again, If you just try generate simple db with one table and e.g. 10 fields,
And you try do something more complex e.g. DISTINCT, or GROUP BY you will
see results that I have mention.

If you will open Activity Monitor (OS X) and watch for usage of RAM you will
see that for one million records table (100MB) Sql Lite eat wow -- 600MB of
RAM. And it takes 30 seconds to resolve e.g. Simple DISTINCT on single
table.

It is very easy extrapolate results to db of size in 5-10-100 times bigger.

So problem is very simple: Like any simple db engine Sql Lite just play in
RAM. Until you application and your users work on SMALL databases which are
about 3-10 times less than installed RAM, it looks fast. AS only your query
will eat more RAM than you have you will hear beep-beep-beep...


-----------------
P.S. Let me say next:

Sql Lite is really cool, fantastic and phenomenal, and its author is great
develoepr. I say this because I have see sources of Sql Lite and see its
ideas.

The most interesting that practically nobody else do not use this way in
database development. But I have ask self: should we try repeat this in
Valentina database? And answer is NO. Because this way applies very strict
limitations. We will never use this way in Valentina database.

And I just warn that developers should see that's limitations very clearly.
If you going to play with DB e.g. of DVD size and do queries more complex
than simple SEARCH BY VALUE -- SqlLite exactly is not good choice.

P.S.2 

I have see one more fantastic database engine which have force me say wow!!!
:-) 

Its size is even 3 times less than SQl Lite. Only 100Kb.
It have in this size very good SQL, ODBC driver!!!, server, HTML interface
to server, and more. FANTASTIC from big letter.

I will not say its name, because it exactly will not help to Rev developers
A) it is RAM database
B) its price is in $80,000 - $300,000   yes this is not typo. :-)
    

P.S.3

But as say my friend and developer of our team -- miracles not exists.
And when we have start study that engines deeply we was able VERY EASY nock
down them with db size and queries that Valentina still is able eat in 0.1
of second. 

That is the difference guys. I think nobody want be catched by case when
your users says: Hey, I have db only in 300MB. Why my query takes few
minutes?!!? Why my HDD spins like a crazy?! :-)

-- 
Best regards,

Ruslan Zasukhin
VP Engineering and New Technology
Paradigma Software, Inc

Valentina - Joining Worlds of Information
http://www.paradigmasoft.com

[I feel the need: the need for speed]