I developed a commercial app with DBISAM 3.x, when the app contains a lot of registers the performance of DBISAM is very slow. I migrated to
MySQL and the performance of MySQL is excellent but I need to pay licences. Im evaluating to migrate to ElevateDB.

How is the performance of ElevateDB against DBISAM 3.x?


Thanks
Alejandro

Alejandro


Performance will depend on specific usage. I can't comment on V3 but moving from V4 my gut reaction is faster ranging from a bit to a lot.

Why not download a trial and run some benchmarks against the operations you're interested in.

Roy Lambert [Team Elevate]

I started with version 3 and I'd have to agree with Roy in that performance
from DBISAM4 to EDB2 is better.

I think the features that Tim has established with EDB and direction it is
taking, EDB is a strong alternative to MySQL.

Not to mention, its a bargain at twice the price.

Lance

"Alejandro Castro" <alejandro@poware.com> wrote in message
news:E7927AF7-296D-4075-A061-688AC147BC46@news.elevatesoft.com...
>I developed a commercial app with DBISAM 3.x, when the app contains a lot
>of registers the performance of DBISAM is very slow. I migrated to
> MySQL and the performance of MySQL is excellent but I need to pay
> licences. Im evaluating to migrate to ElevateDB.
>
> How is the performance of ElevateDB against DBISAM 3.x?
>
>
> Thanks
> Alejandro
>

Alejandro,

>>How is the performance of ElevateDB against DBISAM 3.x?

I haven't noticed a performance difference between DBISAM 3 and 4. After switching to EDB
I experienced a performance nightmare...which was bit by bit resolved by fixes from Tim
and EDB specific optimizations of my code.

Now the app, in most areas, is running faster than it did with DBISAM.

Heiko

Lance,

<< Not to mention, its a bargain at twice the price. >>

I don't think I've ever seen *that* statement before.

Also, a general statement regarding ElevateDB performance:

I've recently managed to put in some pretty nice improvements to the query
optimizer and indexing code, so 2.02 B4 should see some pretty decent
performance improvements overall.  I've got one LOJ query in particular that
a customer sent, that previously took 43 seconds now takes about 2.1
seconds.  Interestingly enough, the customer is a DBISAM customer, and the
same optimizer improvement will be in the next DBISAM build.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim

May I ask you what and where have you found it ? It will require reindexing
something or the process of indexing will be faster ? I don´t really start
many questions here but I am curious about it.

Eduardo

Eduardo,

<< May I ask you what and where have you found it ? >>

The improvement to the LOJs involves queries like this:

SELECT *
FROM MyTable LEFT OUTER JOIN MyOtherTable ON
MyTable.MyColumn=MyOtherTable.MyColumn AND
MyOtherTable.MyOtherColumn=100

IOW, LOJs that also include a non-join condition in the LOJ expression.

The other improvement is to the general index navigation/updating, and will
result in about a 10-20% reduction in execution time for most operations.

<< It will require reindexing something or the process of indexing will be
faster ? >>

The latter (indexing will be faster).

--
Tim Young
Elevate Software
www.elevatesoft.com