Skip to content

Instantly share code, notes, and snippets.

@dbaltas

dbaltas/gist:4672866

Last active February 8, 2019 01:16
Download ZIP

Revisions

  1. dbaltas revised this gist Jan 30, 2013. 1 changed file with 5 additions and 2 deletions.
    7 changes: 5 additions & 2 deletions gistfile1.txt
    View file
    Original file line number Diff line number Diff line change
    @@ -8,7 +8,8 @@ Our application is on Zend Framework 1.12, php 5.4, phpunit 3.5.15 and mysql 5.5
    Our test suite has 13000 unit tests and is taking around 22 minutes to run on our testing environment.

    Most of the tests have (unfortunately) heavy database access.
    The problem is that running phpunit on multiple processes accessing a single same database generates many deadlocks.
    The problem is that running phpunit on multiple processes accessing a single same database
    generates many deadlocks.

    We want to have paratest processes run on different test databases to avoid deadlocks.
    This approach would require each child process to connect a separate database.
    @@ -20,7 +21,9 @@ When it runs out of available tokens, no new process can be created.
    When a process ends, the token that was used by this process becomes available.

    Any ideas/concerns on this?
    In any event we will be working on this implementation in the next couple of days so maybe you can give it a review or follow up after we are done on our paratest fork, https://github.com/tripsta/paratest.
    In any event we will be working on this implementation in the next couple of days so maybe
    you can give it a review or follow up after we are done
    on our paratest fork, https://github.com/tripsta/paratest.

    In general we are willing to collaborate/contribute on the project.

  2. dbaltas created this gist Jan 30, 2013.
    29 changes: 29 additions & 0 deletions gistfile1.txt
    View file
    Original file line number Diff line number Diff line change
    @@ -0,0 +1,29 @@
    Hi Brian, @brianium

    Congratulations on Paratest.
    It is a very well written project.

    We (as tripsta organization) want to run our test suite in parallel.
    Our application is on Zend Framework 1.12, php 5.4, phpunit 3.5.15 and mysql 5.5.
    Our test suite has 13000 unit tests and is taking around 22 minutes to run on our testing environment.

    Most of the tests have (unfortunately) heavy database access.
    The problem is that running phpunit on multiple processes accessing a single same database generates many deadlocks.

    We want to have paratest processes run on different test databases to avoid deadlocks.
    This approach would require each child process to connect a separate database.

    A suggested solution is:
    The main process has a pool of tokens.
    When it starts a new child process it passes a token to it.
    When it runs out of available tokens, no new process can be created.
    When a process ends, the token that was used by this process becomes available.

    Any ideas/concerns on this?
    In any event we will be working on this implementation in the next couple of days so maybe you can give it a review or follow up after we are done on our paratest fork, https://github.com/tripsta/paratest.

    In general we are willing to collaborate/contribute on the project.


    Keep on the good work!