Hi there.
I've built and been running the following on a ubuntu 15.10 VM (12 Mb RAM) - Win7 Native - with encypted drive, Intel i7-4790k @ 4Ghz - 32GB Ram :
ahh - no svn info equivalent with git - ok - last commit info
commit 3a4db6346b2b1b4c3e3733d833f338d104f7da95
Merge: 0eb3b66 7f77b23
Author: Riccardo Spagni <ric@spagni.net>
Date: Sun Dec 13 22:17:07 2015 +0200
Merge pull request #533
7f77b23 posix_daemonizer: only create the main daemon object in the last child (moneromooo-monero)
Some feedback - the RAM usage is much better, but the syncing process is hammering my harddrive, to the point where not only the VM becomes unresponsive (10-20 second pauses but VM is still stable), but also any disk access on my native machine significantly slows down applications running there.
Changing limit_up and limit_down values has little effect.
I'm going to have a little peek at the database code tonight to get familiar to see how its working.
Just wanted to give a heads up as I suspect when the next database version is released you may find the complaints switching from RAM usage to HDD usage.
Good points. But when you think about it, given that the database is going to be around 10 GB and it is possible under ideal conditions to sync in a about an hour, that is going to be a lot of disk writing over the course of that hour. There is probably value in a "background sync" mode that deliberately takes longer with a less intense workload. A better implementation of down_limit would probably do the trick. Obviously that can come later after 0.9.
Also, I have to say that an SSD is pretty recommended here. HDD does work, but obviously for any database-type workload with a lot of random access, SSD is just going to work much better.
Thanks for the test report and any further effort put into testing.
