Could you try to profile and see where the time is spent? LLVM 3.7 (used on
0.5) is known to be significantly slower in compile time than LLVM 3.3
(used on 0.4).
On Friday, August 12, 2016 at 8:52:42 AM UTC-7, Uwe Fechner wrote:
>
> Thanks your hard work!
>
> Nevertheless I am a little bit disappointed with the time, needed for
> including my own code.
> With Julia 0.5.0rc2 it needs 11.5 s, with Julia 0.4.6 it was only 6.34 s.
> Is this to be expected?
>
> I am using packages like PyPlot and JuMP, but I think they are precompiled.
>
> (On Ubuntu 16.06, 64 bits).
>
> Julia 0.5.0 rc2
>
> julia> tic();include("Plotting.jl");toc()
> Min (nonlinear expression)
> Subject to
> 1 nonlinear constraint
> 0.15 ≤ area ≤ 2500
> 60 ≤ height ≤ 500
> elapsed time: 11.500368527 seconds
> 11.500368527
>
> julia> tic();aenarete();toc()
>
>
> ******************************************************************************
> This program contains Ipopt, a library for large-scale nonlinear
> optimization.
> Ipopt is released as open source code under the Eclipse Public License
> (EPL).
> For more information visit http://projects.coin-or.org/Ipopt
>
> ******************************************************************************
>
> elapsed time: 7.29577799 seconds
> 7.29577799
>
>
> ------------------------------------------------------------------------------
>
> Julia 0.4.6
>
> julia> tic();include("Plotting.jl");toc()
> Min (nonlinear expression)
> Subject to
> 1 nonlinear constraint
> 0.15 ≤ area ≤ 2500
> 60 ≤ height ≤ 500
> elapsed time: 6.347609088 seconds
> 6.347609088
>
> julia> tic();aenarete();toc()
>
>
> ******************************************************************************
> This program contains Ipopt, a library for large-scale nonlinear
> optimization.
> Ipopt is released as open source code under the Eclipse Public License
> (EPL).
> For more information visit http://projects.coin-or.org/Ipopt
>
> ******************************************************************************
>
> elapsed time: 6.116511336 seconds
> 6.116511336
>
> On Friday, August 12, 2016 at 2:38:20 PM UTC+2, Tony Kelman wrote:
>>
>> I have just tagged and uploaded release candidate 2 for Julia version
>> 0.5.0. Binaries are available from
>>
>>
>> https://s3.amazonaws.com/julialang/bin/linux/x64/0.5/julia-0.5.0-rc2-linux-x86_64.tar.gz
>>
>>
>> https://s3.amazonaws.com/julialang/bin/linux/x86/0.5/julia-0.5.0-rc2-linux-i686.tar.gz
>>
>>
>> https://s3.amazonaws.com/julialang/bin/osx/x64/0.5/julia-0.5.0-rc2-osx10.7+.dmg
>>
>>
>> https://s3.amazonaws.com/julialang/bin/winnt/x64/0.5/julia-0.5.0-rc2-win64.exe
>>
>>
>> https://s3.amazonaws.com/julialang/bin/winnt/x86/0.5/julia-0.5.0-rc2-win32.exe
>>
>> https://s3.amazonaws.com/julialang/bin/checksums/julia-0.5.0-rc2.sha256
>> https://s3.amazonaws.com/julialang/bin/checksums/julia-0.5.0-rc2.md5
>> For gpg signatures (with this key http://julialang.org/juliareleases.asc)
>> of the Linux tar.gz binaries, append .asc to the filename.
>>
>> (arm binaries are taking a while to build, I will upload them later - we
>> will also put links to this release candidate on the web site soon)
>>
>> The primary thing this does not yet include that we do plan on getting
>> into the final 0.5.0 release is proxy support for the package manager. A
>> preliminary version of that has been merged to master but still has some
>> build system issues that need to be worked out. We will put out a release
>> candidate 3 next week that will hopefully have this resolved, along with
>> any other major bug fixes that happen by then. If all goes well and no
>> major blocking issues come up after that, RC3 could possibly be the last
>> release candidate and promoted to final, but we will see how it goes next
>> week. Follow the progress at
>> https://github.com/JuliaLang/julia/issues/17418 and please report any
>> issues you find.
>>
>> -Tony
>>
>>
