Hard Disk (HDD) Space Usage Disproportional
8 Aug 2015 9:06:18 UTC
Topic 198182
(moderation:
Einstein @ HOME is using a disproportionally large amount of hard disk space compared to other BOINC projects.
Could I have set up something wrong in Preferences? I've looked and each project appears to have the same settings, anything special needed to stop this?
Does the application need some optimisation? I'm using Linux Mint 17.1 64bit.
E@H is using c.580Mb with no Tasks present. Other project use 1-10Mb, except POGS @ Home which also has an issue(?) using c.220Mb with no Task present.
Happy to send other system data and screen shots (if I knew how).
Hard Disk (HDD) Space Usage Disproportional
)
Hi PeteEAH welcome to E@H.
No, this is normal.
I would say no, but you may need to choose what projects and applications you want to run, and some run better (depending on the resources available).
Different applications in different projects keep reference data files for different lengths of times as each task may reuse the data, and downloading it each time would be time consuming. (apps have different system needs if you like - some apps are heavy GPU users, others heavy HDD users etc)
You are running the S6Bucket Follow-up application and it is HDD heavier than others. This important S6Bucket thread here is worth reading.
I'm reasonably certain boinc's "project resource share" functionality (which apportions CPU resources) is not used to directly apportion disk free space (or other resouce - such as bandwidth etc)
On your system the path may be different, i can see the application files for E@H here
/var/lib/boinc-client/projects/einstein.phys.uwm.edu/
and the configuration files here
/var/lib/boinc-client/
and i allocate about 10GB to boinc, and it seems to manage that space reasonably well.
The Project preferences page can help with choosing apps.
I tend to run single project (and usually a single favoured application) and if i feel like sharing i then switch processing to another.
RE: Einstein @ HOME is
)
Einstein downloads a large amount of data and then runs a bunch of workunits off of that data, meaning you get a few large downloads instead of lots of littler ones. Periodically it will replace that huge file with a new one, and in most cases delete the older one. There have been reports by a few people of the old ones not deleting properly, you can search the forums for those threads, but most people have no problems.