Prev: ssGetInputPortWidth
Next: Problems with Regress
From: Stephen Lienhard on 12 Jan 2010 12:22 "Vesal " <vesal(a)yahoo.com> wrote in message <hii9dg$g2c$1(a)fred.mathworks.com>... > > We have a similar set up. But each MCR instance takes about 40meg. (not including calcs) > > The initial memory is about 40MB for us too. However, once a function call is made, it increases to about 200-250MB (due to the loading of MATLAB toolbox functions). True. We went through a few options and our conclusion was: it didn't matter if we kept it in memory or loaded them each time it was executed as long as there was enough total memory on the machine to handle a service for each core. So we eventually opted for loading the mcr/service each time a job ran (yes with a 2 second delay of loading the mcr) because of simplicity. If we kept them running in memory we were still OK with the 200meg b/c the total memory was OK. fyi We run 8 cores with 2 gig per core on each machine. If I felt a job would run past the 2 gig I would utilize a memory mapped file in matlab. This way I had the stability of knowing I would never run out of memory. Just sharing our approach. We have been running for 4+ years now with very few issues. Stephen |