Another thing to consider is how many files
you are working with and creating in a day.
I am easily in the hundreds and that could
make things worse than for someone who
is just working with the same few files.

John Balgenorth


On Jul 28, 2015, at 12:59 PM, JB <sund...@pacifier.com> wrote:

> Okay I did not remember your statement
> correctly.  But I have noticed after 50%
> things start slowing down a little.  And if
> I get to 20% they have slowed down a lot.
> I do agree at 10% you are risking damage
> but I would say from the poor performance
> I have seen at 20% it suggest the drive is
> rising damage.  30% and above seems to
> work a lot better for me.  Even 10% seems
> to be a lot of wasted space since on a 1TB
> drive that is around 100gb.  That is how it
> works for me and it is not limited to 1 drive.
> As for the memory I usually only have one
> app open at a time so that is not a problem.
> 
> John Balgenorth
> 
> 
> On Jul 28, 2015, at 8:49 AM, Bob Sneidar <bobsnei...@iotecdigital.com> wrote:
> 
>> You do not remember correctly. What I said (if I am remembering correctly) 
>> is that you need at least the size of your memory free and then some. This 
>> is because your OS will page out your memory into virtual memory, which is 
>> just a disk cache. But other apps also need room to grow for other things. I 
>> have always maintained that 10% is a red line you should never cross without 
>> risking damage to the OS or other apps data.
>> 
>> Bob S
>> 
>> 
>> On Jul 24, 2015, at 08:19 , Richard Gaskin 
>> <ambassa...@fourthworld.com<mailto:ambassa...@fourthworld.com>> wrote:
>> 
>> If I remember correctly Bob Sneidar said that a
>> you need at least 1/2 of your hard drive as free
>> space to run efficiently.  So if you have a drive
>> with 500 GB you need 250 GB or more free
>> space on the drive.  Anything below that and
>> it normal operations like opening files will be
>> slower.  I have used more space than 1/2 and
>> the more I use the slower it gets.  Sometimes
>> you can speed things up a little by relaunching
>> the Finder.  That can be done using the Force
>> Quit option.  If it speeds things up it will only be
>> a temporary fix.
>> 
>> John Balgenorth
>> 
>> _______________________________________________
>> use-livecode mailing list
>> use-livecode@lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your subscription 
>> preferences:
>> http://lists.runrev.com/mailman/listinfo/use-livecode
>> 
> 
> 
> _______________________________________________
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription 
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
> 


_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Reply via email to