And they say OpenBase is good?

[Frank Bitterlich]

LOL... Ruslan, I can see your point.

I had to make the choice for our business DB backend recently, and
OpenBase was one of the two products I was testing. I got similar
results to yours, but I'm not sure if that really counts, since I didn't
look to deep into the possibilities on how to optimize it.

In the end I chose the other product (Frontbase), but mostly because it
adheres very stict to the SQL92 standard. But the performance results I
got were almost the same: Not even the same league as Valentina.

There are two things I wrote that off to: First, it is a server DBMS,
and I expect it to have a more linear performance (read: not getting
slower) with multiple, concurrent accesses. I have no way to know how
Valentina Server will behave inthis respect,, but as it was originally
developer as as single user DB, I think you might run into problems in
this respect. But I'm open for surprises :)

The second factor is the cache and index optimisations. In my 500 000
record test database, I got speed differences between 20 seconds and 0.1
seconds for the same query, depending on cache situation and -settings.
I'm confident that when I go into production with this database, I will
be able to tune it (with the help of the Frontbase guys, whose support
is almost as good as yours :) to much greater speed.

But still Valentina continues to amaze me. Today I had a corrupted ValDB
(well, not really corrupted, but garbage data inside) and had to do an
XML dump/edit/load to fix it. When I did the dump of the 40 000 records,
I was waiting, and waiting, and waiting for the export to begin, not
realizing that it all was already done in a fraction of a second. :) I
think even BBEdit took longer to save the text file after I had edited it...

Maybe you want to contact the Openbase guys and ask them if you could
tune your test DB some way...

Cheers,
   Frank+++


Ruslan Zasukhin wrote:
> 
> Hi Guys,
> Hi Totte, Norman.
> 
> Today we with Yuri have at last of end download and install OpenBase to play
> with it...
> 
> For tests I have made in V4RB Example1 db with million records.
> Then from VAPP I have export this db  (65MB) into text file.
> We have create analog db and table in OpenBase and import file.
> 
> Totte, you was right, if Valentina import/export such file In about 30
> seconds on my DUAL 867, then OpenBase do this about hour. I have told you
> that this can be because they do this in transaction mode, but in Import
> dialog it was OFF.
> 
> Okay, after we have drink 10 cups of coffee, we have got table for test.
> 
> By the way, I am in deep shock on size of this db in OpenBase -- 380MB(!!!)
> 
> ---
> I was stupid enough to make simplest
>     SELECT * FROM Person
> 
> This must select million records.
> Guys, we again have wait an hour to see result:
>     find 18 seconds     (print 3600 seconds)
> 
> Valentina do this query
>     in 0.01 second.
> 
> -----
> I have try to do non-indexed search on ushort field.
> SEARCH was from 18 seconds to 30 seconds.
> The same search in Valentina 0.1-0.2 second.
> 
> -----
> Okay, we have now have add index to ushort_fld (this was fast enough).
> 
> Now the same search on ushort_fld > 32600 that find 2500 records
> take 0.3 - 0.9 seconds.
> 
> Search that find 40000 records take more time (as usual for any RDBMS).
> 
> -----
> I was going to see speed of sort of all million of records, but I do not
> want spend another hour of my life...
> 
> ---
> Question: may be exists some way, to NOT "print records" in OpenBase???
> And in any case I so wonder what it do so many time ???
> 
> ----
> Somebody have told me that OpenBase have great GUI.
> I cannot say this. IT looks of course better of VAPP's GUI, because it is OS
> X native, but in general .... Not great. Normal RDBMS way.
> 
> Although 2 ideas I like.
> Jochen, I think you can repeat them in Valentina Studio.
> 1) I like idea of Import Dialog,, when we see table from imported file, and
> we can drag fields on headers of columns to build map.
> 2) I like idea of Relation dialog with TABs.
> 
>     By the way. OpenBase do not have Cascade deletion ?
>     Releation Dialog do not have such option.
> 
> ------
> Another point. OpenBase creates on default (and you cannot change this as I
> see) 3 fields in total 20 bytes PER RECORD (!!!)
>     id (8 bytes)
>     timestamp (8 bytes)
>     version (4 bytes)
> 
> ------
> RESUME:
> 
> After some guys have told me very good words about Openbase,
> I have worry if to be frankly. :-)
> 
> Now I am cool again. OpenBase is regular RDBMS with predicted results.
> I see that Valentina is much faster even on this simple tests.
> I have not meet things that have impress me.
> 
> And as I describe this on benchmark pages,
> The more complex query, the more loose regular RDBMS to Valentina.
> 


--
Günter Schmidt & Co. oHG         
Frank Bitterlich             eMail: bitterlich at gsco.de
Schlosserstr. 4              WWW:   http://www.gsco.de/gsco
D-60322 Frankfurt            Tel.:  069 / 156809-29
GERMANY                      Fax:   069 / 156809-28