Hi,
I am a proud owner of a 2008 octocore 2.8 mac pro, and there is a thing that is increasingly annoying me... Mostly I let the macpro sleep when I am not using it, and very often, when I get it out of sleep, I have to wait between one and two minutes for it to become usable, time during which the harddrives are, it seems, moving around huge amounts of data...
Note that the system is built with 16Gb of ram, and almost always has huge amounts of ram available to the system.
The activity monitor doesn't tell me much about the process that triggers such amount of activity on the harddrive... I suspect some caching with safari 4, but I am not sure...
Surprisingly, I never noticed the same phenomenom with my white nvidia macbook, which reactivity in those moments is putting the macpro to shame...
One last information : the leopard partition is a 390Gb partition on a samsung 500Gb 7200rpm hd, and it is 60% empty...
Apart from buying a SSD (which I am not even sure would be a good solution, as the harddrive operations I am complaining about involve a lot of writing...) what could I do ?
phjo
I am a proud owner of a 2008 octocore 2.8 mac pro, and there is a thing that is increasingly annoying me... Mostly I let the macpro sleep when I am not using it, and very often, when I get it out of sleep, I have to wait between one and two minutes for it to become usable, time during which the harddrives are, it seems, moving around huge amounts of data...
Note that the system is built with 16Gb of ram, and almost always has huge amounts of ram available to the system.
The activity monitor doesn't tell me much about the process that triggers such amount of activity on the harddrive... I suspect some caching with safari 4, but I am not sure...
Surprisingly, I never noticed the same phenomenom with my white nvidia macbook, which reactivity in those moments is putting the macpro to shame...
One last information : the leopard partition is a 390Gb partition on a samsung 500Gb 7200rpm hd, and it is 60% empty...
Apart from buying a SSD (which I am not even sure would be a good solution, as the harddrive operations I am complaining about involve a lot of writing...) what could I do ?
phjo