Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 12 replies
  • Subscribers 1 subscriber
  • Views 4183 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Disk fragmentation

MawfTech

Why does Sophos AU cause so much fragmentation?

Each minor update downloads but a few KB however every time there's something to do, the entire SAV package is copied (that's > 70Mb's), the new IDE is then integrated and then this entire package is copied back again. This huge > 140MB copy which occurs several times a day is destroying small disk partitions causing machines to grind to a halt during the update cycle.

I'm pretty sure we've all experienced this slowdown and it's time to start making Sophos aware of this so we get a change. It makes no sense at all to copy the entire installation folder each time there's an update. It makes no sense to copy it again once the IDE's added. The process should happen in-place i.e.. checksum the install folder and integrate the update directly. Don't copy the folder. This way, we dramatically reduce fragmentation and speed up the whole update process.

I've got users with typically < 60% disk usage so 'ideal' and plenty of RAM. Give them 3 weeks and the machine always says 'you should defragment this volume' and it's always because the Sophos updates. Anyone else out there have users groaning every five minutes that they can't look at the screen at the moment 'cause Sophos is updating. Now you know why!

Matt

:1720


This thread was automatically locked due to age.
Parents
  • 0

    Thanks John,

    I'm glad you're aware of this. It's becoming more noticeable as the install package gets larger and larger. More and more fragmentation occurs with larger copies and with the role out of EPS v.9, typically I'm seeing 2-3 weeks before I've got > 30% fragmentation whereas that was around 3-4 months on v.7. It's just the shear package size and the necessary frequency of updates that's causing this.

    FYI, typical machine to observe would be a P4 2.4Ghz running XP-Pro SP3, around 30Gb's disk capacity which I state to my users should remain at < 60% usage (although most seem to run around 70-75%). Bigger disks reduces the problem but then if you give users bigger disks, they go fill them up unecessarily and that's another issue.

    Matt

    P.S. Would be interested in any betas trials relating to this.....

    :1753
Reply
  • 0

    Thanks John,

    I'm glad you're aware of this. It's becoming more noticeable as the install package gets larger and larger. More and more fragmentation occurs with larger copies and with the role out of EPS v.9, typically I'm seeing 2-3 weeks before I've got > 30% fragmentation whereas that was around 3-4 months on v.7. It's just the shear package size and the necessary frequency of updates that's causing this.

    FYI, typical machine to observe would be a P4 2.4Ghz running XP-Pro SP3, around 30Gb's disk capacity which I state to my users should remain at < 60% usage (although most seem to run around 70-75%). Bigger disks reduces the problem but then if you give users bigger disks, they go fill them up unecessarily and that's another issue.

    Matt

    P.S. Would be interested in any betas trials relating to this.....

    :1753
Children
No Data
Unfiltered HTML