Did you reset the project to get a different wrapper, or was in inclusive of new wu's?

VBoxwrapper v200 is coming from BOINC's developer team: https://boinc.berkeley.edu/dl/vboxwrapper_26200_windows_x86_64.exe

btw: I changed the memory setting to 3072MB again.

We updated the project to provide vboxwrapper_26200 for Windows.

We updated the project to provide vboxwrapper_26200 for Windows.

Well done! Waiting for more substantial queue

Is there a way to reduce the i/o?

If I run this project it seems to write several GB every minute on my ssd.

If I run this project it seems to write several GB every minute on my ssd.

Thanks for the warning. I haven't received any work to even check it.

But I use a write-cache (or place the BOINC Data folder on a ramdisk) in that case.
For Windows, I use PrimoCache or Primo Ramdisk Pro (Dataram RAMDisk also works).
For Linux, you can set up a write cache of any size by just increasing the parameters of the built-in write cache.

Of course, you need enough DRAM to do any good; probably 2 GB at least, though I usually do 8 to 12 GB for the cache/ramdisk (beyond what you otherwise need).
If anyone needs setup info, I can provide it; even better if/when I get any work to test it out here.

Can you give us the workunit id for the job that is writing so much? That is very unusual behavior, and we want to investigate why that is happening. Thanks.

Unfortunatly not.

Currently I am testing a few settings. Maybe it was a boinc problem, Boinc startet 6 tasks parallel which seems to be to much for my ram (16 gb).
I think I have to write an App config.xml to limit it to 3 tasks.

But I will observe if it happens again.

Somehow your application seems to be a bit…. weird.

I have a ryzen 1800x so it has 8 real cores, 16 threads. for a "cool" running Computer i let it run max 8 "hyperthreaded cores". Lets my Computer be sweet and smooth.

Unfortunately, your app does not behave well in boinc (or the vbox config isnt nice)

a) it is multithreaded. from my Observation, every vbox instance is suited for using all avail cores (so for me, 8-threaded). When running inside boinc it does not Show ist multithreaditivy. so it runs multiple instances clogging up the puter to heatmax. it starts 8 instances - i dont have 64 cores!

b) it seems to use up to 4 gig every instance. But the mem usage is not reported (or put in before running) to BOINC. So even if my Computer would be able to run multiple instances of multicore WUs, it also reaches my max RAM. (which is what some other also describe as "hard drive over-usage " - it is the constant swap file read/write.

Since your app managed to crash my windows into BSOD twice I have suspended it until you fix some issues. By the way: the boinc developers or some techy-guru-people here in forums may be able to help you on some of the settings.

=Lupus= aka the "Alpha Testers Anonymous" wolf in sheep disguise

I did not see any multi-threaded work units. They each ran on a single core of my i7-3770 (Ubuntu 16.04, VBox 5.1.38).

But I did see high write-rates; about 190 GB/day (total for all the cores), though I did not notice which ones. I will check it again when I get more.

We updated the project to provide vboxwrapper_26200 for Windows.

Well done! Waiting for more substantial queue

So the wu's are playing nicely now for me. I have been using an app_config file to limit the wu's to 4 on an I7 with 16Gb ram. I changed it to 6 and nanohub works with 4 wu's and 2 waiting on memory. This is a big step forward.