[julia-users] High memory consumption with loops

2016-08-24 Thread Venil Noronha
The following code seems to consume a lot of memory. Could anyone spot what I'm doing wrong here? I'm also using the JuMP library. function initUtilityConstraint() c = categories[1] me = attack_methods[1] t = teams[1] tuple = Simulate.cmt(c, me, t) w = windows[1] r = resou

Re: [julia-users] High memory consumption with loops

2016-08-24 Thread Tim Holy
What have you tried so far? See http://docs.julialang.org/en/latest/manual/ performance-tips/#tools, esp. @code_warntype. --Tim On Wednesday, August 24, 2016 1:55:23 PM CDT Venil Noronha wrote: > The following code seems to consume a lot of memory. Could anyone spot what > I'm doing wrong here? I

Re: [julia-users] High memory consumption with loops

2016-08-24 Thread Venil Noronha
I've just been able to @time the loop so far to see allocations at iteration level. I haven't yet tried @code_warntype; I'll probably do that next and see if I can get somewhere. Thanks, Venil On Wednesday, August 24, 2016 at 5:37:17 PM UTC-7, Tim Holy wrote: > > What have you tried so far? See

Re: [julia-users] High memory consumption with loops

2016-08-24 Thread Venil Noronha
I've also tried to @profile, however, julia libraries seem to be executed the most. Venil On Wednesday, August 24, 2016 at 11:16:53 PM UTC-7, Venil Noronha wrote: > > I've just been able to @time the loop so far to see allocations at > iteration level. I haven't yet tried @code_warntype; I'll p

Re: [julia-users] High memory consumption with loops

2016-08-25 Thread vavasis
I don't have any suggestions about the performance, but I do have a code correctness suggestion. It appears from your code snippet that you are using dictionaries called "effectiveness" and "resource_fines", and that the keys to these dictionaries are a mutable type. This can lead to subtle p

Re: [julia-users] High memory consumption with loops

2016-08-30 Thread Venil Noronha
Thanks Steve! The problem was finally found to be with some matrix operations. We've used an alternate approach and it seems to be fixed now. Venil On Thursday, August 25, 2016 at 6:41:25 PM UTC-7, vav...@uwaterloo.ca wrote: > > I don't have any suggestions about the performance, but I do have