Is it possible to force a specific program to remain in memory after closing it? Announcing the arrival of Valued Associate #679: Cesar Manara Planned maintenance scheduled April 23, 2019 at 00:00UTC (8:00pm US/Eastern) Should an RSS feed of hot network questions feed any chat room(s) here?Mute specific programMacMini crashing after changing memory?Crashes and hangs after memory DOWNgradeI run out of RAM on a 8GB MacBook Pro 15"How to test memory after memory upgrade?Many applications hanging after OS 10.9.5 updateIs it possible to exclude bad memory?Why does iTunes think that it is quitting “unexpectedly” every time I quit?Unable to Cmd+Tab after closing applicationApps crashes after Memory Upgrade

Can you explain what "processes and tools" means in the first Agile principle?

What is the difference between globalisation and imperialism?

A letter with no particular backstory

How to unroll a parameter pack from right to left

Why can't I install Tomboy in Ubuntu Mate 19.04?

Is it possible to give , in economics, an example of a relation ( set of ordered pairs) that is not a function?

How often does castling occur in grandmaster games?

Lagrange four-squares theorem --- deterministic complexity

Can a new player join a group only when a new campaign starts?

Should there be a hyphen in the construction "IT affin"?

How to run automated tests after each commit?

How does light 'choose' between wave and particle behaviour?

Hangman Game with C++

Quadrilaterals with equal sides

Aligning an equation at multiple points, with both left and right alignment, as well as equals sign alignment

What order were files/directories outputted in dir?

What to do with repeated rejections for phd position

Take 2! Is this homebrew Lady of Pain warlock patron balanced?

Would it be easier to apply for a UK visa if there is a host family to sponsor for you in going there?

Amount of permutations on an NxNxN Rubik's Cube

What is the meaning of 'breadth' in breadth first search?

Do wooden building fires get hotter than 600°C?

How does the math work when buying airline miles?

File name problem(?)



Is it possible to force a specific program to remain in memory after closing it?



Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 23, 2019 at 00:00UTC (8:00pm US/Eastern)
Should an RSS feed of hot network questions feed any chat room(s) here?Mute specific programMacMini crashing after changing memory?Crashes and hangs after memory DOWNgradeI run out of RAM on a 8GB MacBook Pro 15"How to test memory after memory upgrade?Many applications hanging after OS 10.9.5 updateIs it possible to exclude bad memory?Why does iTunes think that it is quitting “unexpectedly” every time I quit?Unable to Cmd+Tab after closing applicationApps crashes after Memory Upgrade



.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;








2















Alfred is great, of course, and I use it all the time. However, if I haven't opened it for a little while it can take a few seconds to open the search-bar UI. Otherwise, it will open in less than a quarter of a second.



I believe this is to do with the fact that it is moved out of memory by the operating system, meaning it has to be copied back in next time I request it (note: I have a mechanical hard-drive, not an SSD, so that takes ages).



So my question is this: can I force macOS to leave an application in main memory even if I'm not using it?










share|improve this question




























    2















    Alfred is great, of course, and I use it all the time. However, if I haven't opened it for a little while it can take a few seconds to open the search-bar UI. Otherwise, it will open in less than a quarter of a second.



    I believe this is to do with the fact that it is moved out of memory by the operating system, meaning it has to be copied back in next time I request it (note: I have a mechanical hard-drive, not an SSD, so that takes ages).



    So my question is this: can I force macOS to leave an application in main memory even if I'm not using it?










    share|improve this question
























      2












      2








      2








      Alfred is great, of course, and I use it all the time. However, if I haven't opened it for a little while it can take a few seconds to open the search-bar UI. Otherwise, it will open in less than a quarter of a second.



      I believe this is to do with the fact that it is moved out of memory by the operating system, meaning it has to be copied back in next time I request it (note: I have a mechanical hard-drive, not an SSD, so that takes ages).



      So my question is this: can I force macOS to leave an application in main memory even if I'm not using it?










      share|improve this question














      Alfred is great, of course, and I use it all the time. However, if I haven't opened it for a little while it can take a few seconds to open the search-bar UI. Otherwise, it will open in less than a quarter of a second.



      I believe this is to do with the fact that it is moved out of memory by the operating system, meaning it has to be copied back in next time I request it (note: I have a mechanical hard-drive, not an SSD, so that takes ages).



      So my question is this: can I force macOS to leave an application in main memory even if I'm not using it?







      macos applications memory






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked 2 hours ago









      ZacZac

      18115




      18115




















          2 Answers
          2






          active

          oldest

          votes


















          2














          MacOS's memory management is quite sophisticated, and it generally does try to keep as much stuff in memory as possible. If Alfred is still running, then it will be in memory.



          If you have quit Alfred, then it might still be retained in memory, which is why it is faster to load next time. However, the OS will clear the quit app from memory, if the memory is needed for something else. So you might experience slowness somewhere else if you don't let the OS clear the quit app.



          Recommendations for improving speed:



          1. Leave Alfred running all the time. If it's slow to come to foreground sometimes, even when its been running in the background, then that's not a memory issue, but something else: possibly related the slowness of the HDD.

          2. Get more RAM, if possible. You don't say what model of Mac and how much RAM.

          3. Replace the HDD with an SSD.





          share|improve this answer























          • I have 8GB of RAM, and I tend to be using about 5GB of that most of the time (according to Activity Monitor). I think your first point, about it relating to the slowness of the HDD, is probably right - though unfortunate because SSDs are annoyingly expensive.

            – Zac
            36 mins ago











          • @Zac SSDs are pretty cheap these days, particularly SATA ones to replace mechanicals. I can see 128 GB ones for £20, €20, $20. That's big enough for your OS and apps at least, which should make a huge difference.

            – benwiggy
            10 mins ago


















          1














          If your goal is to simply keep an application running all the time even when you close it you could use the method described here in this articled titled: Always keep an application open .



          In that article they describe using this method for the Stickies application.



          Steps



          Excerpted here in case it ever gets deleted


          For example, to keep Stickies permanently open, remove Stickies from
          the login items for your account (if you've placed it there), quit
          Stickies, and then create the following plist file in the LaunchAgents
          folder of your home Library (~/Library/LaunchAgents) with the name
          user.launchkeep.stickies.plist:



          <?xml version="1.0" encoding="UTF-8"?>
          <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
          <plist version="1.0">
          <dict>
          <key>Label</key>
          <string>user.launchkeep.stickies</string>
          <key>KeepAlive</key>
          <true/>
          <key>Program</key>
          <string>/Applications/Stickies.app/Contents/MacOS/Stickies</string>
          </dict>
          </plist>


          Now load this launchd job by logging out of your account and logging
          back in or launch Terminal and enter:



          $ launchctl load ~/Library/LaunchAgents/user.launchkeep.stickies.plist


          Stickies will now effectively be un-removable -- any time it quits,
          crashes, or gets forced-quit it will pop right back up. If fact, in
          order to quit the app at any time other than logout or shutdown you'll
          need to disable the job; In Terminal type:



          $ launchctl remove user.launchkeep.stickies 


          Or you can set up a script that does that for you.







          share|improve this answer























          • Thanks, I'll give that a try

            – Zac
            43 mins ago


















          2 Answers
          2






          active

          oldest

          votes








          2 Answers
          2






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          2














          MacOS's memory management is quite sophisticated, and it generally does try to keep as much stuff in memory as possible. If Alfred is still running, then it will be in memory.



          If you have quit Alfred, then it might still be retained in memory, which is why it is faster to load next time. However, the OS will clear the quit app from memory, if the memory is needed for something else. So you might experience slowness somewhere else if you don't let the OS clear the quit app.



          Recommendations for improving speed:



          1. Leave Alfred running all the time. If it's slow to come to foreground sometimes, even when its been running in the background, then that's not a memory issue, but something else: possibly related the slowness of the HDD.

          2. Get more RAM, if possible. You don't say what model of Mac and how much RAM.

          3. Replace the HDD with an SSD.





          share|improve this answer























          • I have 8GB of RAM, and I tend to be using about 5GB of that most of the time (according to Activity Monitor). I think your first point, about it relating to the slowness of the HDD, is probably right - though unfortunate because SSDs are annoyingly expensive.

            – Zac
            36 mins ago











          • @Zac SSDs are pretty cheap these days, particularly SATA ones to replace mechanicals. I can see 128 GB ones for £20, €20, $20. That's big enough for your OS and apps at least, which should make a huge difference.

            – benwiggy
            10 mins ago















          2














          MacOS's memory management is quite sophisticated, and it generally does try to keep as much stuff in memory as possible. If Alfred is still running, then it will be in memory.



          If you have quit Alfred, then it might still be retained in memory, which is why it is faster to load next time. However, the OS will clear the quit app from memory, if the memory is needed for something else. So you might experience slowness somewhere else if you don't let the OS clear the quit app.



          Recommendations for improving speed:



          1. Leave Alfred running all the time. If it's slow to come to foreground sometimes, even when its been running in the background, then that's not a memory issue, but something else: possibly related the slowness of the HDD.

          2. Get more RAM, if possible. You don't say what model of Mac and how much RAM.

          3. Replace the HDD with an SSD.





          share|improve this answer























          • I have 8GB of RAM, and I tend to be using about 5GB of that most of the time (according to Activity Monitor). I think your first point, about it relating to the slowness of the HDD, is probably right - though unfortunate because SSDs are annoyingly expensive.

            – Zac
            36 mins ago











          • @Zac SSDs are pretty cheap these days, particularly SATA ones to replace mechanicals. I can see 128 GB ones for £20, €20, $20. That's big enough for your OS and apps at least, which should make a huge difference.

            – benwiggy
            10 mins ago













          2












          2








          2







          MacOS's memory management is quite sophisticated, and it generally does try to keep as much stuff in memory as possible. If Alfred is still running, then it will be in memory.



          If you have quit Alfred, then it might still be retained in memory, which is why it is faster to load next time. However, the OS will clear the quit app from memory, if the memory is needed for something else. So you might experience slowness somewhere else if you don't let the OS clear the quit app.



          Recommendations for improving speed:



          1. Leave Alfred running all the time. If it's slow to come to foreground sometimes, even when its been running in the background, then that's not a memory issue, but something else: possibly related the slowness of the HDD.

          2. Get more RAM, if possible. You don't say what model of Mac and how much RAM.

          3. Replace the HDD with an SSD.





          share|improve this answer













          MacOS's memory management is quite sophisticated, and it generally does try to keep as much stuff in memory as possible. If Alfred is still running, then it will be in memory.



          If you have quit Alfred, then it might still be retained in memory, which is why it is faster to load next time. However, the OS will clear the quit app from memory, if the memory is needed for something else. So you might experience slowness somewhere else if you don't let the OS clear the quit app.



          Recommendations for improving speed:



          1. Leave Alfred running all the time. If it's slow to come to foreground sometimes, even when its been running in the background, then that's not a memory issue, but something else: possibly related the slowness of the HDD.

          2. Get more RAM, if possible. You don't say what model of Mac and how much RAM.

          3. Replace the HDD with an SSD.






          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered 1 hour ago









          benwiggybenwiggy

          1,603312




          1,603312












          • I have 8GB of RAM, and I tend to be using about 5GB of that most of the time (according to Activity Monitor). I think your first point, about it relating to the slowness of the HDD, is probably right - though unfortunate because SSDs are annoyingly expensive.

            – Zac
            36 mins ago











          • @Zac SSDs are pretty cheap these days, particularly SATA ones to replace mechanicals. I can see 128 GB ones for £20, €20, $20. That's big enough for your OS and apps at least, which should make a huge difference.

            – benwiggy
            10 mins ago

















          • I have 8GB of RAM, and I tend to be using about 5GB of that most of the time (according to Activity Monitor). I think your first point, about it relating to the slowness of the HDD, is probably right - though unfortunate because SSDs are annoyingly expensive.

            – Zac
            36 mins ago











          • @Zac SSDs are pretty cheap these days, particularly SATA ones to replace mechanicals. I can see 128 GB ones for £20, €20, $20. That's big enough for your OS and apps at least, which should make a huge difference.

            – benwiggy
            10 mins ago
















          I have 8GB of RAM, and I tend to be using about 5GB of that most of the time (according to Activity Monitor). I think your first point, about it relating to the slowness of the HDD, is probably right - though unfortunate because SSDs are annoyingly expensive.

          – Zac
          36 mins ago





          I have 8GB of RAM, and I tend to be using about 5GB of that most of the time (according to Activity Monitor). I think your first point, about it relating to the slowness of the HDD, is probably right - though unfortunate because SSDs are annoyingly expensive.

          – Zac
          36 mins ago













          @Zac SSDs are pretty cheap these days, particularly SATA ones to replace mechanicals. I can see 128 GB ones for £20, €20, $20. That's big enough for your OS and apps at least, which should make a huge difference.

          – benwiggy
          10 mins ago





          @Zac SSDs are pretty cheap these days, particularly SATA ones to replace mechanicals. I can see 128 GB ones for £20, €20, $20. That's big enough for your OS and apps at least, which should make a huge difference.

          – benwiggy
          10 mins ago













          1














          If your goal is to simply keep an application running all the time even when you close it you could use the method described here in this articled titled: Always keep an application open .



          In that article they describe using this method for the Stickies application.



          Steps



          Excerpted here in case it ever gets deleted


          For example, to keep Stickies permanently open, remove Stickies from
          the login items for your account (if you've placed it there), quit
          Stickies, and then create the following plist file in the LaunchAgents
          folder of your home Library (~/Library/LaunchAgents) with the name
          user.launchkeep.stickies.plist:



          <?xml version="1.0" encoding="UTF-8"?>
          <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
          <plist version="1.0">
          <dict>
          <key>Label</key>
          <string>user.launchkeep.stickies</string>
          <key>KeepAlive</key>
          <true/>
          <key>Program</key>
          <string>/Applications/Stickies.app/Contents/MacOS/Stickies</string>
          </dict>
          </plist>


          Now load this launchd job by logging out of your account and logging
          back in or launch Terminal and enter:



          $ launchctl load ~/Library/LaunchAgents/user.launchkeep.stickies.plist


          Stickies will now effectively be un-removable -- any time it quits,
          crashes, or gets forced-quit it will pop right back up. If fact, in
          order to quit the app at any time other than logout or shutdown you'll
          need to disable the job; In Terminal type:



          $ launchctl remove user.launchkeep.stickies 


          Or you can set up a script that does that for you.







          share|improve this answer























          • Thanks, I'll give that a try

            – Zac
            43 mins ago















          1














          If your goal is to simply keep an application running all the time even when you close it you could use the method described here in this articled titled: Always keep an application open .



          In that article they describe using this method for the Stickies application.



          Steps



          Excerpted here in case it ever gets deleted


          For example, to keep Stickies permanently open, remove Stickies from
          the login items for your account (if you've placed it there), quit
          Stickies, and then create the following plist file in the LaunchAgents
          folder of your home Library (~/Library/LaunchAgents) with the name
          user.launchkeep.stickies.plist:



          <?xml version="1.0" encoding="UTF-8"?>
          <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
          <plist version="1.0">
          <dict>
          <key>Label</key>
          <string>user.launchkeep.stickies</string>
          <key>KeepAlive</key>
          <true/>
          <key>Program</key>
          <string>/Applications/Stickies.app/Contents/MacOS/Stickies</string>
          </dict>
          </plist>


          Now load this launchd job by logging out of your account and logging
          back in or launch Terminal and enter:



          $ launchctl load ~/Library/LaunchAgents/user.launchkeep.stickies.plist


          Stickies will now effectively be un-removable -- any time it quits,
          crashes, or gets forced-quit it will pop right back up. If fact, in
          order to quit the app at any time other than logout or shutdown you'll
          need to disable the job; In Terminal type:



          $ launchctl remove user.launchkeep.stickies 


          Or you can set up a script that does that for you.







          share|improve this answer























          • Thanks, I'll give that a try

            – Zac
            43 mins ago













          1












          1








          1







          If your goal is to simply keep an application running all the time even when you close it you could use the method described here in this articled titled: Always keep an application open .



          In that article they describe using this method for the Stickies application.



          Steps



          Excerpted here in case it ever gets deleted


          For example, to keep Stickies permanently open, remove Stickies from
          the login items for your account (if you've placed it there), quit
          Stickies, and then create the following plist file in the LaunchAgents
          folder of your home Library (~/Library/LaunchAgents) with the name
          user.launchkeep.stickies.plist:



          <?xml version="1.0" encoding="UTF-8"?>
          <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
          <plist version="1.0">
          <dict>
          <key>Label</key>
          <string>user.launchkeep.stickies</string>
          <key>KeepAlive</key>
          <true/>
          <key>Program</key>
          <string>/Applications/Stickies.app/Contents/MacOS/Stickies</string>
          </dict>
          </plist>


          Now load this launchd job by logging out of your account and logging
          back in or launch Terminal and enter:



          $ launchctl load ~/Library/LaunchAgents/user.launchkeep.stickies.plist


          Stickies will now effectively be un-removable -- any time it quits,
          crashes, or gets forced-quit it will pop right back up. If fact, in
          order to quit the app at any time other than logout or shutdown you'll
          need to disable the job; In Terminal type:



          $ launchctl remove user.launchkeep.stickies 


          Or you can set up a script that does that for you.







          share|improve this answer













          If your goal is to simply keep an application running all the time even when you close it you could use the method described here in this articled titled: Always keep an application open .



          In that article they describe using this method for the Stickies application.



          Steps



          Excerpted here in case it ever gets deleted


          For example, to keep Stickies permanently open, remove Stickies from
          the login items for your account (if you've placed it there), quit
          Stickies, and then create the following plist file in the LaunchAgents
          folder of your home Library (~/Library/LaunchAgents) with the name
          user.launchkeep.stickies.plist:



          <?xml version="1.0" encoding="UTF-8"?>
          <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
          <plist version="1.0">
          <dict>
          <key>Label</key>
          <string>user.launchkeep.stickies</string>
          <key>KeepAlive</key>
          <true/>
          <key>Program</key>
          <string>/Applications/Stickies.app/Contents/MacOS/Stickies</string>
          </dict>
          </plist>


          Now load this launchd job by logging out of your account and logging
          back in or launch Terminal and enter:



          $ launchctl load ~/Library/LaunchAgents/user.launchkeep.stickies.plist


          Stickies will now effectively be un-removable -- any time it quits,
          crashes, or gets forced-quit it will pop right back up. If fact, in
          order to quit the app at any time other than logout or shutdown you'll
          need to disable the job; In Terminal type:



          $ launchctl remove user.launchkeep.stickies 


          Or you can set up a script that does that for you.








          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered 1 hour ago









          slmslm

          1,237816




          1,237816












          • Thanks, I'll give that a try

            – Zac
            43 mins ago

















          • Thanks, I'll give that a try

            – Zac
            43 mins ago
















          Thanks, I'll give that a try

          – Zac
          43 mins ago





          Thanks, I'll give that a try

          – Zac
          43 mins ago



          Popular posts from this blog

          Category:Fedor von Bock Media in category "Fedor von Bock"Navigation menuUpload mediaISNI: 0000 0000 5511 3417VIAF ID: 24712551GND ID: 119294796Library of Congress authority ID: n96068363BnF ID: 12534305fSUDOC authorities ID: 034604189Open Library ID: OL338253ANKCR AUT ID: jn19990000869National Library of Israel ID: 000514068National Thesaurus for Author Names ID: 341574317ReasonatorScholiaStatistics

          Reverse int within the 32-bit signed integer range: [−2^31, 2^31 − 1]Combining two 32-bit integers into one 64-bit integerDetermine if an int is within rangeLossy packing 32 bit integer to 16 bitComputing the square root of a 64-bit integerKeeping integer addition within boundsSafe multiplication of two 64-bit signed integersLeetcode 10: Regular Expression MatchingSigned integer-to-ascii x86_64 assembler macroReverse the digits of an Integer“Add two numbers given in reverse order from a linked list”

          Kiel Indholdsfortegnelse Historie | Transport og færgeforbindelser | Sejlsport og anden sport | Kultur | Kendte personer fra Kiel | Noter | Litteratur | Eksterne henvisninger | Navigationsmenuwww.kiel.de54°19′31″N 10°8′26″Ø / 54.32528°N 10.14056°Ø / 54.32528; 10.14056Oberbürgermeister Dr. Ulf Kämpferwww.statistik-nord.deDen danske Stats StatistikKiels hjemmesiderrrWorldCat312794080n790547494030481-4