[Swift-user] Memory is a serious issue

Mihael Hategan hategan at mcs.anl.gov
Thu Dec 6 16:52:05 CST 2012

Unfortunately, there are no aces down the sleeve at this point.

When it's ready, Swift/T might provide better scalability.
If I have time, I might upgrade the Swift/K engine to the same end.

The simple things you can do now are:
- Don't run swift on login nodes. This won't solve the memory problem,
but it won't tax the login nodes.
- De-couple the coaster service (if you are using that) from swift by
running it non-local. This might give you some more memory for swift


On Thu, 2012-12-06 at 10:39 -0600, Lorenzo Pesce wrote:
> Hi! 
> It is me again. 
> Discounting for my manifest inability of using swift intelligently, it seems that to runs simulations we need *a lot* of RAM (8+ GB for the large sims, say > 10^6 app runs, which is taxing on the login nodes). Any idea about how we can reduce out memory footprint?
> Otherwise, I just sent a 300K sim as a small test and it seems to work. (I call it a small test because the next one is going to be in the 10G size).
> Lorenzo
> _______________________________________________
> Swift-user mailing list
> Swift-user at ci.uchicago.edu
> https://lists.ci.uchicago.edu/cgi-bin/mailman/listinfo/swift-user

More information about the Swift-user mailing list