Does any one has experience with both derby and Mysql ? performance comparesion

Hi
Thank you for reading my post.
does any one has don a ttest to compare both Mysql and derby , in regard to
Tra/second or
insert/select statement execution time ?
I had chance to use mysql 5 or Derby for a 20-30 tra/second application .
now which one is better to user , and perform better for my case.
Thank you so much

Please can some on share his/her knowledge about this item.
It will help me so much to complete my job.


On 11/17/05, Legolas Woodland <legolas.w-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>
> Hi
> Thank you for reading my post.
> does any one has don a ttest to compare both Mysql and derby , in regard
> to Tra/second or
> insert/select statement execution time ?
> I had chance to use mysql 5 or Derby for a 20-30 tra/second application .
> now which one is better to user , and perform better for my case.
> Thank you so much
>

Legolas Woodland wrote:

> Please can some on share his/her knowledge about this item.
> It will help me so much to complete my job.

The best advice is usually to test your own application, or code that
mimics your application. Ensure you perform the database operations
fully and don't take short-cuts. I've seen very bad benchmarks over the
years, for example executing rs = ps.executeQuery() but never processing
the ResultSet, ie. not fetching the rows or columns. Also it's good to
ensure the test performs what you think it meant to do, usually by
running test sql after the performance runs, e.g. if I expected 100,000
orders to be added, check they actually there in the database.

This presentation shows Derby faster than MySQL and MySQL faster than
Derby. :-)

Derby was faster when the database was larger than the memory
MySQL was faster when the database was smaller than the memory

http://www3.java.no/JavaZone/2005/pr...byJavaZone.pdf

I know since those numbers there have been some fixes and interesting
discoveries by the Sun team in Norway that improves Derby's performance.

Dan.

On Friday 18 November 2005 15:58, Legolas Woodland wrote:
> Please can some on share his/her knowledge about this item.
> It will help me so much to complete my job.
>
> On 11/17/05, Legolas Woodland <legolas.w-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> > Hi
> > Thank you for reading my post.
> > does any one has don a ttest to compare both Mysql and derby , in regard
> > to Tra/second or
> > insert/select statement execution time ?
> > I had chance to use mysql 5 or Derby for a 20-30 tra/second application .
> > now which one is better to user , and perform better for my case.
> > Thank you so much

You're going to have to provide a little bit more information.

Because of Derby-47, depending on the planned queries you may run, Derby may
not be your best choice.

--
Michael Segel
Principal
MSCC

This is a good presentation. Thanks Bernt, (and anyone else) for putting
this together.

This doesn't seem to be linked from Apache Derby site. Should it be?

Satheesh

Daniel John Debrunner wrote:

> Derby was faster when the database was larger than the memory
>
>MySQL was faster when the database was smaller than the memory
>
>http://www3.java.no/JavaZone/2005/pr...byJavaZone.pdf
>
>I know since those numbers there have been some fixes and interesting
>discoveries by the Sun team in Norway that improves Derby's performance.
>
>Dan.
>
>
>
>
>

Satheesh Bandaram wrote:
> This is a good presentation. Thanks Bernt, (and anyone else) for putting
> this together.
>
> This doesn't seem to be linked from Apache Derby site. Should it be?

I think we should move all these types of links to a page on the Derby
Wiki so that when a terrific link is found, whoever found it can update
the Wiki.

If anyone wants to go ahead and set up a Wiki page, that'd be terrific.
Otherwise, I'll set one up next week -- and will also start looking at
what on the web site might be best moved to the Wiki.

-jean


> Satheesh
>
> Daniel John Debrunner wrote:
>
>
>>Derby was faster when the database was larger than the memory
>>
>>MySQL was faster when the database was smaller than the memory
>>
>>http://www3.java.no/JavaZone/2005/pr...byJavaZone.pdf
>>
>>I know since those numbers there have been some fixes and interesting
>>discoveries by the Sun team in Norway that improves Derby's performance.
>>
>>Dan.
>>
>>
>>
>>
>>
>
>