Boinc's maximum cache is 1k WU's/per machine. it will eventually figure out what is what it considers the optimum cache. back in the day, AMD's ruled, then it was Intel's, today on the newer hardware it's kinda even, neither has any real advantage in my opinion, the latest Threadrippers really haven't been out long enough to tell but look like they will be a bit of a step forward for AMD.ĪS far as Boinc and process management, it's slow. the CPU difference isn't that far apart at this point. Generally, Most projects favor Linux particularly the grid projects. Easiest way to find out is to look at the projects host stats page, it will tell you what the host producing the most are running for both CPU & OS. Most people run one GPU project and one different CPU project leaving a CPU core open for each instance of a GPU application running.Ĭache: Me, I run with the full 10 days and 10 extra days in boinc cause I want the largest cache possible. Then use the app_config file to limit the number of cores a project can use. If you wish to run two different CPU projects on the same computer you need a resource controller like Process Lasso where you can dedicate a certain number of cores to certain processes. Generally GPU and CPU does not mix on the same project. Some projects have both a GPU and CPU application. In general you can run two different projects per machine, one GPU the other CPU. Has anyone tried the projects with advantages in Linux inside of a virtual machine? Are the gains worthwhile? Or even the Linux subsystem within Windows 10. What do folks use to track actual daily credits per machine rather than RAC? That seems to be wildly varying for some odd reason on the same computer with the same project, and we won't even talk about two different projects.I've been using BAM, but the "new" design is very much not screen reader friendly. Maybe I just need to be patient and wait a few months? Or should I be setting this to more or less? Deadlines are being met so maybe I'm just overcomplicating things. It either overcompensates or doesn't fetch enough because it doesn't think the CPU will be able to finish what it has. It seems like it takes boinc a while to settle down and figure out just how much work amounts to 0.5 days, though. Right now I have 0.1 days minimum with up to an additional 0.5. That being said, what are some best practices for running multiple CPU projects? How many days of boinc cached work is a reasonable amount (apart from bunkering). Why have resource management if Boinc clearly doesn't respect it? ![]() I've been suspending Universe in the meantime and micromanaging myself. I have Universe set for at 10 total resources and amicable set for 100 (or the default), just as an example, yet Universe has been steadily crunching for the last week or more. I've noticed that Boinc really doesn't know how to manage resources I set for a project. In doing so I've found a few oddities that maybe someone can help answer. ![]() I've been attempting to figure out which CPU projects favor Intel's (usually anyway) advantage in IPC and AVX (Primegrid) and which favors AMD's multithreading (Amicable). So I'm relatively new to this multi project thing.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |