Hi  Adam

It is great that you recognize this as an issue!

So I thought I would start a new thread where I could post my performance 
related issues :)

>On my machine in the US, I can run a compete build and test in 30
>minutes or so.

So the ideal objective would be to reach somewhere close to this.

The hardware setup I have is a core 2 duo proc @ 2.33Ghz , Ram 2 GB.

Time taken is well

        -it takes me anywhere between 40-70 min to reach the acceptance testing 
part, that was where the tests gave up on me yesterday

        -today I have been running just the acceptance testing, [btw the 
suggested solution to revert back to older versions of the firefox browser 
actually worked], it has been more than 2 hrs and the tests are still running. 
[ I finally found enough time to read 'neverwhere' :) ]

Suggestions that have already been made include

1) Setting the mysql config value for innodb_flush_log_at_trx_commit ,in 
my.ini, to 0

2) Do just the tests that are required. i.e do the integration, junit, 
acceptance tests separately.

> Another idea is to only run the tests that you know are covering your area - 
> while you are developing. You  
> can run both unit, integration, and acceptance tests individually from 
> Eclipse and also from maven on the 
> command line. Are you doing this? This is sure to be quicker than running all 
> the tests all the time. You can > debug the problems with Selenium this way - 
> run one test inside eclipse. If that works, then run one test from > the 
> command line. If that doesn't work, you can debug it easier, and re-run in a 
> minute, rather than 71 
> minutes.

Well I don't really get the setup described here. It is probably because I have 
never used eclipse for anything apart from just navigating the project and 
searching for code to modify :P . I have almost always used the command line 
for all the build functionalities. I will look at this more closely on Monday.

Well these are my notes on this issue. It would be brilliant if I can reduce my 
build+test times to your level! :)

If need be I can send any of my configuration files that any of the processes 
might be using.

Thank you and regards
Chandan Rao
Sungard Technology Services





-----Original Message-----
From: Adam Feuer [mailto:[email protected]] 
Sent: Saturday, September 12, 2009 6:40 AM
To: Mifos functional discussions
Subject: Re: [Mifos-functional] [Mifos-developer] FEATURE: enforcedagerangefor 
new clients

On Fri, Sep 11, 2009 at 8:18 PM,  <[email protected]> wrote:
> But I have run into more, this time with acceptance testing ( it takes  71 
> min to come to this !).
[...]
> It is extremely frustrating that I have the patch 'all ready' but its taking 
> unacceptable amount of time to confirm that it is indeed 'all ready'. :(

Chandan,

The tests are slow and that is frustrating! However, they should not
be that slow. I'll be traveling back the US, but will you work with
Udai, Adam, Van, and others on the list to debug the slowness problem?
I think we can help you get it going faster.

On my machine in the US, I can run a compete build and test in 30
minutes or so. This is still too slow! But it is better than 71
minutes. We are working on making the build faster - the reason it's
slow right now is that we've been making improvements to the test
suite so that the tests can run independently. Now that is done, we
will be breaking the application/ module into other smaller modules,
and making the smaller modules run faster.

Unfortunately, to make things better in the long run, we had to make
them worse in the short run. But our idea is that we will make it
faster soon.

Another idea is to only run the tests that you know are covering your
area - while you are developing. You can run both unit, integration,
and acceptance tests individually from Eclipse and also from maven on
the command line. Are you doing this? This is sure to be quicker than
running all the tests all the time. You can debug the problems with
Selenium this way - run one test inside eclipse. If that works, then
run one test from the command line. If that doesn't work, you can
debug it easier, and re-run in a minute, rather than 71 minutes.

 If you need help getting set up do this, let us know!

-adam
-- 
Adam Feuer <adamf at pobox dot com>

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Mifos-functional mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mifos-functional



------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Mifos-functional mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mifos-functional

Reply via email to