![]() ![]() Also it can be useful for users who work with applications that use high quantities of memory, applications that leave useless allocated memory after their processes are closed. In conclusion: this is a good tool for computers that have small amounts of memory installed. #Ifreemem review freePluses: it can free memory, it has some interesting built in tools: 'Memory Allocation Benchmark', and 'Memory Logger'.ĭrawbacks / flaws: it makes some applications work sluggish after the optimization process, but this is just a temporary issue. The benchmark has a 'Suggest' button that places a suggested value for the memory that should be allocated by the test. The benchmark can measure the time that is taken by the allocation of a given amount of memory. I am talking about the 'Memory Logger' that can keep a log of your used memory, and about the 'Memory Allocation Benchmark'. IFreeMem features some interesting built in tools. The advantage, of course, its the extra free memory that is gained after the optimization process. The reallocation is a disadvantage of all applications that can do the same job as this one. After the memory optimization process is finished some of your application can work a little slower till they reallocate the memory. The memory optimization process can work pretty fast even though during the process your computer might act a little sluggish. It won't put you in difficulty because it has only one button and the rest is done automatically. The interface of this application is very simple. This is why I said "you may also want to try out a program such as iFreeMem" to confirm the issue is not being caused by whatever program or plugin not releasing memory correctly.IFreeMem is a simple utility that has the ability to recover the wasted memory of your Mac. but that's not quite the same issue as a failure to free up memory as can be found using K4 or even some versions of Omnisphere (when going through the presets) The example you gave, is a good one which, as you said, running something like iFM would not resolve. The other reason I suggested using a Mem free program is that Kontakt (4.x) seems to incorrectly hold on to memory without freeing it up when not in use and so the use of such a program as iFM resolves this issue nicely. whereas I have had issues running purge with Logic running at the same time. However, the reason why i suggested using iFreeMem (or another similar program) is that for whatever technical reason, it doesn't cause issues with Logic when ran, while Logic is still active. ![]() I know exactly what you mean and yes, you can use the purge command instead. Use iFreemem Utilities such as iFreemem can help free RAM from the system and other applications by putting a temporary heavy demand for RAM on the system. iFreemem would help reclaim that memory without having to quit Logic and reload everything. I often use this when dealing with certain plugins (and Kontakt was one of them) that do not completely free up memory when removed or no longer being used. To remedy this you might also want to try out a program like iFreeMem (There are several others on the App Store but I find iFreeMem to be the most efficient) and run it after you have loaded up Logic to see if it can reduce the overall memory footprint used. To Test, remove all instances of Kontakt from a template and save Template./ Quit Logic and restart and examine Activity to see if Wired RAM has dropped. Whatever is using up so much Wired RAM is what is draining your resources. My guess is it will be Kontakt's Mem Server(s) that is reserving RAM as i would imagine in your Template you have instances of Kontakt. Think of it as 'hard wired' RAM reserved by an application or something running within or by an application. Wired RAM is memory that cannot be off loaded by the OS to disk. I admittedly don't really understand the different types of "wired, Active, Inactive" ram, but I do notice that my computer starts sputtering once I run out of free ram. But it seems like my computer fills up my ram capacity regardless of how much I have. I recently upgraded from 10 to 14 gigs of ram because of this issue. The rest of my computer's Ram usage is negligible. Looking at my Activity monitor, Logic, Vienna and my Kontakt Memory server add up to 8.5 Gigs. Logic starts sputtering about, and I have to reboot my machine to get running smoothly again (Which sucks because booting up a logic template with 8 gigs of samples takes a long ass time) And after working for a while I suddenly notice in my Activity Monitor that I have 41.6 MB of ram, 4.2 Gigs Active, 2.5 Gigs Inactive, and 7.3 Gigs wired. When I start up my computer, and open up logic, I tells me I have about 4-6 gigs of free ram. The issue is that I inevitably run out of Ram. I'm running a pretty big template in logic (64bit) with an internal instance of Vienna Ensemble Pro. Wondering if anyone can shed any light on this. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |