You are viewing a plain text version of this content. The canonical link for it is here.
Posted to olio-dev@incubator.apache.org by "Shanti Subramanyam (JIRA)" <ji...@apache.org> on 2009/01/26 20:47:59 UTC

[jira] Created: (OLIO-42) Driver using think time instead of cycle time

Driver using think time instead of cycle time
---------------------------------------------

                 Key: OLIO-42
                 URL: https://issues.apache.org/jira/browse/OLIO-42
             Project: Olio
          Issue Type: Bug
          Components: php-driver
            Reporter: Shanti Subramanyam
            Assignee: Shanti Subramanyam


UIDriver.java in the driver should specify the cycleType as CycleType.CYCLETIME. But it is specified as CycleType.THINKTIME. This causes a problem where the final ops/sec from a run is much lower than expected since the use of think time increases the cycle. This in turn causes a valid run to fail because of the criteria that the reported ops/sec should be < users/5.25.

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


[jira] Closed: (OLIO-42) Driver using think time instead of cycle time

Posted by "Shanti Subramanyam (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/OLIO-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Shanti Subramanyam closed OLIO-42.
----------------------------------


> Driver using think time instead of cycle time
> ---------------------------------------------
>
>                 Key: OLIO-42
>                 URL: https://issues.apache.org/jira/browse/OLIO-42
>             Project: Olio
>          Issue Type: Bug
>          Components: php-driver
>            Reporter: Shanti Subramanyam
>            Assignee: Shanti Subramanyam
>
> UIDriver.java in the driver should specify the cycleType as CycleType.CYCLETIME. But it is specified as CycleType.THINKTIME. This causes a problem where the final ops/sec from a run is much lower than expected since the use of think time increases the cycle. This in turn causes a valid run to fail because of the criteria that the reported ops/sec should be < users/5.25.

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


[jira] Resolved: (OLIO-42) Driver using think time instead of cycle time

Posted by "Shanti Subramanyam (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/OLIO-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Shanti Subramanyam resolved OLIO-42.
------------------------------------

    Resolution: Fixed

Modified:
    incubator/olio/workload/php/trunk/src/com/sun/web20/driver/UIDriver.java

Modified: incubator/olio/workload/php/trunk/src/com/sun/web20/driver/UIDriver.java
URL: http://svn.apache.org/viewvc/incubator/olio/workload/php/trunk/src/com/sun/web20/driver/UIDriver.java?rev=737850&r1=737849&r2=737850&view=diff
==============================================================================
--- incubator/olio/workload/php/trunk/src/com/sun/web20/driver/UIDriver.java (original)
+++ incubator/olio/workload/php/trunk/src/com/sun/web20/driver/UIDriver.java Mon Jan 26 21:13:16 2009
@@ -51,7 +51,7 @@
           }
 )
 @NegativeExponential (
-    cycleType = CycleType.THINKTIME,
+    cycleType = CycleType.CYCLETIME,
     cycleMean = 5000,
     cycleDeviation = 2
 )

> Driver using think time instead of cycle time
> ---------------------------------------------
>
>                 Key: OLIO-42
>                 URL: https://issues.apache.org/jira/browse/OLIO-42
>             Project: Olio
>          Issue Type: Bug
>          Components: php-driver
>            Reporter: Shanti Subramanyam
>            Assignee: Shanti Subramanyam
>
> UIDriver.java in the driver should specify the cycleType as CycleType.CYCLETIME. But it is specified as CycleType.THINKTIME. This causes a problem where the final ops/sec from a run is much lower than expected since the use of think time increases the cycle. This in turn causes a valid run to fail because of the criteria that the reported ops/sec should be < users/5.25.

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