Re: svn commit: r1327411 - in /ofbiz/trunk: bin/ tools/functions.sh tools/git-rebase-runner.sh

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
23 messages Options
12
Reply | Threaded
Open this post in threaded view
|

Re: svn commit: r1327411 - in /ofbiz/trunk: bin/ tools/functions.sh tools/git-rebase-runner.sh

Jacopo Cappellato-4
Jacques,

here are some details:

Hardware Overview:

  Model Name: MacBook Pro
  Model Identifier: MacBookPro8,2
  Processor Name: Intel Core i7
  Processor Speed: 2.2 GHz
  Number of Processors: 1
  Total Number of Cores: 4
  L2 Cache (per Core): 256 KB
  L3 Cache: 6 MB
  Memory: 8 GB

HD details are:

Intel 6 Series Chipset:

  Vendor: Intel
  Product: 6 Series Chipset
  Link Speed: 6 Gigabit
  Negotiated Link Speed: 3 Gigabit
  Description: AHCI Version 1.30 Supported

Hitachi HTS725050A9A362:

  Capacity: 500.11 GB (500,107,862,016 bytes)
  Model: Hitachi HTS725050A9A362                
  Queue Depth: 32
  Rotational Rate: 7200

Jacopo

On Apr 19, 2012, at 9:58 AM, Jacques Le Roux wrote:

> OK seems after all that I need a brand new CPU, hence a new box...
> I must say with the SSDs when running run-tests my CPU is always at 100% (I put the run-tests process priority level to idle to be able to continue other tasks)
> Do you have a SSD in your laptop Jacopo?
>
> Jacques
>
> From: "Jacopo Cappellato" <[hidden email]>
>> On Apr 18, 2012, at 6:55 PM, Jacopo Cappellato wrote:
>>
>>> On Apr 18, 2012, at 6:43 PM, Adam Heath wrote:
>>>
>>>> It currently takes my desktop 1 hour to
>>>> run a full test suite.  clean, load-demo(30m), run-tests(30m).  It
>>>> used to take 12-15m.
>>>
>>> wow, it takes me 2-3 minutes in my laptop.
>>>
>>> Jacopo
>>>
>>
>>
>> To be more precise:
>> (less than) 3 minutes for load-demo
>> 4 minutes and 3 seconds for run-tests
>>
>> Jacopo

Reply | Threaded
Open this post in threaded view
|

Re: svn commit: r1327411 - in /ofbiz/trunk: bin/ tools/functions.sh tools/git-rebase-runner.sh

Adam Heath-2
In reply to this post by Jacopo Cappellato-4
On 04/18/2012 11:33 PM, Jacopo Cappellato wrote:

>
> On Apr 18, 2012, at 7:37 PM, Adam Heath wrote:
>
>> On 04/18/2012 12:28 PM, Jacopo Cappellato wrote:
>>> On Apr 18, 2012, at 7:20 PM, Adam Heath wrote:
>>>
>>>> ps: I am going to switch <if> in ant *back* to javascript, *away* from
>>>> ant-contrib.  The latter is significantly slower when using a system
>>>> installed ant.
>>>
>>> No please, don't do that.
>>
>> I've pointed out a problem, and I have a solution.  Don't just respond
>> saying don't do that, without a reason.  That isn't enough to stop me.
>
> I thought that all the recent threads about code refactoring, moving out custom code etc... were enough to motivate my response; but it seems that you ignored all of them and now pretend a response from me, for such a trivial and small topic.
> The reason is that we want to keep code as clean as possible, as slim as possible (ok, I know it looks silly if you look at the code now... but we are determined to work on this): using an external tool for this instead of custom code is a step in this direction.
> The stats below show that the problem is trivial: it is only relevant when you use your own ant that is not what we recommend; and it is something that should be fixed with the ant community: in fact we want to increase the cooperation with other communities (especially if they are in the ASF world) rather than blobbing everything into OFBiz.

I didn't ignore them all, I've been away and haven't had time to keep
uptodate.

I haven't committed anything for this yet, once you said you had
issues with the switch.  I have 130 commits in my local ofbiz tree,
keeping some out is *not* a problem  (for instance, that salted-based
password change I've kept around for about 2 years).

This explanation is a *good* one.  And yes, I do realize that the
problem is with ant, even system level shouldn't be running as slow as
it is.
Reply | Threaded
Open this post in threaded view
|

Re: svn commit: r1327411 - in /ofbiz/trunk: bin/ tools/functions.sh tools/git-rebase-runner.sh

Adam Heath-2
In reply to this post by Jacopo Cappellato-4
On 04/19/2012 03:15 AM, Jacopo Cappellato wrote:

> Jacques,
>
> here are some details:
>
> Hardware Overview:
>
>   Model Name: MacBook Pro
>   Model Identifier: MacBookPro8,2
>   Processor Name: Intel Core i7
>   Processor Speed: 2.2 GHz
>   Number of Processors: 1
>   Total Number of Cores: 4

So 4 threads.  That doesn't help that much, unless the test suite is
multithreaded now.

>   L2 Cache (per Core): 256 KB
>   L3 Cache: 6 MB
>   Memory: 8 GB
>
> HD details are:
>
> Intel 6 Series Chipset:
>
>   Vendor: Intel
>   Product: 6 Series Chipset
>   Link Speed: 6 Gigabit
>   Negotiated Link Speed: 3 Gigabit
>   Description: AHCI Version 1.30 Supported
>
> Hitachi HTS725050A9A362:
>
>   Capacity: 500.11 GB (500,107,862,016 bytes)
>   Model: Hitachi HTS725050A9A362                
>   Queue Depth: 32
>   Rotational Rate: 7200
>
> Jacopo
>
> On Apr 19, 2012, at 9:58 AM, Jacques Le Roux wrote:
>
>> OK seems after all that I need a brand new CPU, hence a new box...
>> I must say with the SSDs when running run-tests my CPU is always at 100% (I put the run-tests process priority level to idle to be able to continue other tasks)
>> Do you have a SSD in your laptop Jacopo?
>>
>> Jacques
>>
>> From: "Jacopo Cappellato" <[hidden email]>
>>> On Apr 18, 2012, at 6:55 PM, Jacopo Cappellato wrote:
>>>
>>>> On Apr 18, 2012, at 6:43 PM, Adam Heath wrote:
>>>>
>>>>> It currently takes my desktop 1 hour to
>>>>> run a full test suite.  clean, load-demo(30m), run-tests(30m).  It
>>>>> used to take 12-15m.
>>>>
>>>> wow, it takes me 2-3 minutes in my laptop.
>>>>
>>>> Jacopo
>>>>
>>>
>>>
>>> To be more precise:
>>> (less than) 3 minutes for load-demo
>>> 4 minutes and 3 seconds for run-tests
>>>
>>> Jacopo
>

12