Current progress

By Andrey Zarudnev | December 8th, 2008 | 6:48 am

Sorry I missed you all last week, I was out sick, and didn’t have the chance to write and comment here. But I’m back in the healthy saddle again, so here we go.

Currently we are preparing the latest build that will have a new code featured. This will be the gradual RAM cache loading in order to decrease the boot time delays. If there will be no problems found with this functionality then the next build will be the Release Candidate with the help file finished (and hope all translations.)

An announcement of a new build will be later today or probably tomorrow. Thanks for your help :)

9 Responses to “Current progress”

  1. decrypt
    Dec 08, 2008

    Wow that’s very very cool. I am looking forward to this new functionality.


  2. Big Muscle
    Dec 08, 2008

    Hello, Could you have a look at this my suggestion. I think it could optimize cache usage – http://www.eboostr.com/closedbeta/feedback/user-dependent-cache/


  3. Cosmin
    Dec 08, 2008

  4. Andrew Zarudnev
    Dec 08, 2008

    OK, sure.


  5. PangOS
    Dec 08, 2008

    I still have a problem, I’m running a new setup (same machine) Added my sata drive for the caching 4096MB and if built the file and filled it 100%. But my Random read speed is still below 10MB/s when it was about 40MB/s before. I hadn’t changed anything but adding 512MB extra RAM, which even if I remove the 512MB RAM now and go back to the 2GB that I had before it doesn’t make a difference.

    Whats going on?


  6. Andrew Zarudnev
    Dec 08, 2008

    PangOS, the speed of the device is measured by randomly reading actual files from the cache. You are using a hard disk for caching (it has high seek delays which eBoostr is actually trying to eliminate by using flash memory). You’ve got more files in the cache, thus you’ve got more seeks during the random read, thus the overall cache speed decreased.


  7. Ilya Elenik
    Dec 08, 2008

    10MB/s is very good random read speed HDD. There was a problem with speed detection in early beta versions, so possible 40mb/s is a wrong value.


  8. Cosmin
    Dec 09, 2008

    if your hdd could do 40megs/s of random read then it must be… a SSD or flash :). now seriously… if you hdd could do 40mb/s of random reads then you would not need eboostr. the usb flash memory is limited to about 30mb/s (sequential or random) because of the interface. firewire a at about 40mb/s… firewire b at about 60mb/s. i’m only talking about the interface speed and not of the flash memory itself. usually the flash memory is slower than 30mb/s.

    ps: my work hdd can do 10,4mb/s according to eboostr.


  9. Andrew Zarudnev
    Dec 10, 2008

    BTW we have 30 MB/s value on one of our test machines. It has a RAID0 config with two SATA II drives.