Such recommendation depends on exactly what the test is doing, I think
you were still changing the test so it is hard to know what it doing
now until you update the descriptions and send out the source. Having
said this I will give advice based one what I saw previously.
1) assuming your benchmar
[
http://issues.apache.org/jira/browse/DERBY-465?page=comments#action_12316752 ]
Peter Kovgan commented on DERBY-465:
Mike and other Derby hackers!
Could you suggest me best parameters to run "multithreading access write" test
on Derby?
What lock,memo
[
http://issues.apache.org/jira/browse/DERBY-465?page=comments#action_12316609 ]
Peter Kovgan commented on DERBY-465:
Hi Mike!
Your comments and help are very important for me and it seems we are coming
together to similar results.
Thank you.
1. Ri
[
http://issues.apache.org/jira/browse/DERBY-465?page=comments#action_12316402 ]
Mike Matrigali commented on DERBY-465:
--
1) I look forward to your subsequent posting the files you are using get your
results. It seems important when publishing
[
http://issues.apache.org/jira/browse/DERBY-465?page=comments#action_12316384 ]
Sunitha Kambhampati commented on DERBY-465:
---
Derby has some debug properties that can be enabled, to print the lock table
information on a timeout. Please see the fo
Peter Kovgan (JIRA) wrote:
[ http://issues.apache.org/jira/browse/DERBY-465?page=comments#action_12316327 ]
Peter Kovgan commented on DERBY-465:
previous error is result of low derby.locks.escalationThreshold
But I don't understand the reason of this
[
http://issues.apache.org/jira/browse/DERBY-465?page=comments#action_12316327 ]
Peter Kovgan commented on DERBY-465:
previous error is result of low derby.locks.escalationThreshold
But I don't understand the reason of this error
5000 rows is defau
[
http://issues.apache.org/jira/browse/DERBY-465?page=comments#action_12316319 ]
Peter Kovgan commented on DERBY-465:
I have also errors in my new WRITE-multithreading test:
Description:
1 thread runs:
Thread Cycle:{
openConnection()
insert(5000
[
http://issues.apache.org/jira/browse/DERBY-465?page=comments#action_12316317 ]
Peter Kovgan commented on DERBY-465:
Also important: last SELECT-multithreading test was done with SELECT without
WHERE clause.
Just SELECT * FROM table.
> Embedded Derby
[
http://issues.apache.org/jira/browse/DERBY-465?page=comments#action_12316316 ]
Peter Kovgan commented on DERBY-465:
Mike,
thank you for your comments.
They are all helpful.
1. Really : update is differ and this is my mistake and I'll take care. New
t
[
http://issues.apache.org/jira/browse/DERBY-465?page=comments#action_12316315 ]
Peter Kovgan commented on DERBY-465:
Mike,
thank you for your comments.
They are all helpful.
1. Really : update is differ and this is my mistake and I'll take care. New
t
[
http://issues.apache.org/jira/browse/DERBY-465?page=comments#action_12316262 ]
Mike Matrigali commented on DERBY-465:
--
note that the results of the select * tests posted at
http://jamie.ideasasylum.com/notebook/index.php?id=4, show 50,000 row select
[
http://issues.apache.org/jira/browse/DERBY-465?page=comments#action_12316259 ]
Mike Matrigali commented on DERBY-465:
--
A question on the derby-pb1.doc. It looks like the update statement used by
derby and the one for pb use 2 totally different field
[
http://issues.apache.org/jira/browse/DERBY-465?page=comments#action_12316236 ]
Peter Kovgan commented on DERBY-465:
Multithreading test I did compromises Derby(at least I think so , but I may
change my opinion...) and I need your suggestions how to i
[
http://issues.apache.org/jira/browse/DERBY-465?page=comments#action_12316233 ]
Peter Kovgan commented on DERBY-465:
Summary time (in seconds) - it is for multithreading results
> Embedded Derby-PointBase comparison
>
[
http://issues.apache.org/jira/browse/DERBY-465?page=comments#action_12316222 ]
Peter Kovgan commented on DERBY-465:
First of all:
Thank you for your answers and good suggestions, I'll try to provide all
information I have to describe my benchmark.
Tru
[
http://issues.apache.org/jira/browse/DERBY-465?page=comments#action_12316146 ]
Mike Matrigali commented on DERBY-465:
--
It is very interesting that the other embedded db's don't seem to need
indexing, again without seeing the ddl
used for those db's i
[
http://issues.apache.org/jira/browse/DERBY-465?page=comments#action_12316139 ]
Mike Matrigali commented on DERBY-465:
--
It looks like indexing has resolved the unexpected performance problem as the
db grows.
As you measured without indexes, derby as
[
http://issues.apache.org/jira/browse/DERBY-465?page=comments#action_12316126 ]
Sunitha Kambhampati commented on DERBY-465:
---
I am posting the comment that Mike Matrigali posted to derby-dev yesterday.
Mike Matrigali
I can't tell from your report
[
http://issues.apache.org/jira/browse/DERBY-465?page=comments#action_12316021 ]
Peter Kovgan commented on DERBY-465:
I will continue testing Derby trying to add possible optimizations, I'll
publish results shortly.
> Embedded Derby-PointBase compariso
20 matches
Mail list logo
