ffc team mailing list archive
-
ffc team
-
Mailing list archive
-
Message #04308
Re: [Branch ~ffc-core/ffc/main] Rev 1684: Change code generation for evaluate_basis and
On 12 September 2011 20:36, Marie E. Rognes <meg@xxxxxxxxx> wrote:
> On 09/12/11 20:00, Marie E. Rognes wrote:
>>
>> On 09/12/11 19:54, Garth N. Wells wrote:
>>>
>>> On 12 September 2011 18:49, Marie E. Rognes<meg@xxxxxxxxx> wrote:
>>>>
>>>> On 09/12/11 19:40, Garth N. Wells wrote:
>>>>>
>>>>> Which compiler options did you use when evaluating the speed up?
>>>>>
>>>> Tested Extrapolation.h with vanilla dolfin (which is dominated by
>>>> evaluate_basis calls). No additional compiler options set.
>>>>
>>>> What are the default compiler options?
>>>>
>>> '-g' for plain JIT, which is dead slow. You should test with at least:
>>>
>>> parameters["form_compiler"]["cpp_optimize"] = True
>>>
>>> in the Python code. This will use '-O2'.
>>>
>>
>> Ok, thanks -- I'll take a closer look.
>>
>
> Take a look at the attached results in old_evaluate_basis.txt (results with
> "old" FFC),
> and new_evaluate_basis.txt (results with "new" FFC) from running the
> attached
> test_evaluate_basis.py.
>
> Acceptable?
>
Looks good.
Garth
> --
> Marie
>
>
>
>
>
References