eBoostr.dat gets fragmented too much

By Big Muscle | January 11th, 2009 | 5:59 am

When I create a cache on secondary HDD, the eBoostr.dat gets fragmented too much on every cache build. Since the cache is stored on HDD, fragmentation will slow down reading.

I suggest that the eBoostr.dat is created in continuous area. Cache performance will increase a lot.

4 Responses to “eBoostr.dat gets fragmented too much”

  1. Ilya Elenik
    Jan 11, 2009

    We do not control the area of file creation – we just ask windows to create file for us.
    Also I think there will not be much speed gain since we do not read this file continuously – this file is randomly accessed.


  2. Big Muscle
    Jan 11, 2009

    When I defragment this file using Defraggler, the computer runs more smoothly.


  3. chris
    Jan 11, 2009

    if eBoostr is using system system memory, then i think eBoostr.dat is read continuously. if eBoostr.dat is fragmented, then booting takes much longer


  4. Big Muscle
    Jan 11, 2009

    eBoostr.dat stored on C:\ (which is used only for RAM cache) is read only once, so it will slow down “only” boot process. But eBoostr.dat stored on other HDDs (used as disk cache) is read for every cache access, so it has bigger impact on performance.

    I have used my secondary HDD, which is not so much silent. So when eBoostr.dat is defragmented, the HDD seems to be silent, but it makes a big noice in other cases (= fragmented cache file)



«
»