{var%20f='http://v.t.sina.com.cn/share/share.php?appkey=1515056452',u=z||d.location,p=['&url=',e(u),'&title=',e(t||d.title),'&source=',e(r),'&sourceUrl=',e(l),'&content=',c||'gb2312','&pic=',e(p||'')].join('');function%20a(){if(!window.open([f,p].join(''),'mb',['toolbar=0,status=0,resizable=1,width=440,height=430,left=',(s.width-440)/2,',top=',(s.height-430)/2].join('')))u.href=[f,p].join('');};if(/Firefox/.test(navigator.userAgent))setTimeout(a,0);else%20a();})(screen,document,encodeURIComponent,'','','https://www.manongdao.com/data/attach/logo/logo.png', '推荐 Anthone 的问题《Predicting DXL Memory and CPU Usage》','https://www.manongdao.com/q-602321.html','页面编码gb2312|utf-8默认gb2312'));){kind=link}
Has anyone had any success in predicting or profiling DXL applications for memory and CPU usage?
I have a script that opens, closes, and modifies modules, possibly hundreds or even thousands of modules. I want to know, or least have a rough idea, how many modules I can run through the script before running out of memory.
Cross posts: