[jira] Updated: (ZOOKEEPER-524) DBSizeTest is not really testing anything

2010-02-19 Thread Benjamin Reed (JIRA)

 [ 
https://issues.apache.org/jira/browse/ZOOKEEPER-524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Benjamin Reed updated ZOOKEEPER-524:


Resolution: Fixed
Status: Resolved  (was: Patch Available)

Committed revision 912052.


 DBSizeTest is not really testing anything
 -

 Key: ZOOKEEPER-524
 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-524
 Project: Zookeeper
  Issue Type: Bug
  Components: server, tests
Reporter: Patrick Hunt
Assignee: Benjamin Reed
Priority: Minor
 Fix For: 3.3.0


 DBSizeTest looks like it should be testing latency, but it doesn't seem to do 
 it (assert is commented out).
 We need to decide if this test should be fixed, or just dropped.
 Also note: this test takes 40seconds on my system. Way too long. Perhaps 
 async create operations should be used
 to populate the database. I also noticed that data size has a big impact on 
 overall test time (1k vs 5 bytes is something
 like a 2x time diff for time to run the test).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Updated: (ZOOKEEPER-524) DBSizeTest is not really testing anything

2010-02-03 Thread Benjamin Reed (JIRA)

 [ 
https://issues.apache.org/jira/browse/ZOOKEEPER-524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Benjamin Reed updated ZOOKEEPER-524:


Status: Patch Available  (was: Open)

there is no patch associated with this since i'm removing a file. i just wanted 
to make sure people saw this issue.

 DBSizeTest is not really testing anything
 -

 Key: ZOOKEEPER-524
 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-524
 Project: Zookeeper
  Issue Type: Bug
  Components: server, tests
Reporter: Patrick Hunt
Assignee: Benjamin Reed
Priority: Minor
 Fix For: 3.3.0


 DBSizeTest looks like it should be testing latency, but it doesn't seem to do 
 it (assert is commented out).
 We need to decide if this test should be fixed, or just dropped.
 Also note: this test takes 40seconds on my system. Way too long. Perhaps 
 async create operations should be used
 to populate the database. I also noticed that data size has a big impact on 
 overall test time (1k vs 5 bytes is something
 like a 2x time diff for time to run the test).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.