I didn't recognize vmstat, a quick search turns up the following... *"vmstat 60 1440* > /path/to/vmstat.`date +%d` This will write to a file every minute for 24 hours then create a new file and start over."
That might be a good candidate to move over to the flash, along with the logs as Andrew suggested. In fact, it's writing more than the logging daemon so you've just doubled the logging load there. [jbd2/mmcblk0p2-] is the ext4 journal - I always find it interesting to see just how large that value gets over time. Make the SDcard read-only and that drops to zero. Keep it running and see what else shows up, anything that pops up there is a possible candidate to move to the USBstick or hdd. The webserver (the image / html files generated by weewx are included in weewx's iotop total) can also be moved over to the flash /USB stick, hdd, whatever. The rorpi HowTo moves the webserver into memory (except for NOAA files - It's been pointed out that if there are a lot of them, they are worth keeping on the drive rather than regenerating.) I haven't thought of a valid reason to keep the www files on disk, they are regenerated constantly. Although there will be an empty page after a weewx restart, but a placeholder could be kept to inform any one unlucky enough to be viewing in that small time window. Cheers Glenn rorpi - read only raspberry pi + weewx: now with scripts <https://github.com/glennmckechnie/rorpi-raspberrypi> On 1 November 2016 at 19:39, Jacek Skowroński <[email protected]> wrote: > Total DISK READ : 0.00 B/s | Total DISK WRITE : 0.00 B/s > Actual DISK READ: 0.00 B/s | Actual DISK WRITE: 0.00 B/s > PID PRIO USER DISK READ DISK WRITE SWAPIN IO> COMMAND > 87 be/3 root 0.00 B 136.00 K 0.00 % 0.03 % > [jbd2/mmcblk0p2-] > 14302 be/4 root 0.00 B 704.00 K 0.00 % 0.00 % python > /usr/bin/weewxd --daemon --pidfile=/var/run/weewx.pid /etc/weewx/weewx.conf > 12435 be/4 pi 0.00 B 24.00 K 0.00 % 0.00 % vmstat 60 1440 > 495 be/4 root 0.00 B 16.00 K 0.00 % 0.00 % rsyslogd -n > > > On Tuesday, November 1, 2016 at 9:28:58 AM UTC+1, Glenn McKechnie wrote: >> >> run iotop as * iotop -oaP * This will show running process's only and >> accumulated totals - run it for a while and you'll get a better feel of >> what's happening as regards total writes. >> >> sqlite write total will be included under the python /usr/bin/weewx total >> - sqlite is a friendlier option for the SDCard >> >> /dev/ttyUSB0 should be dealt with in memory, no disk access involved >> >> logging will be visible under iotop as rsyslogd -n (or whatever daemon >> you use). Turns out, it's not as big a burden as it's made out to be; at >> least on the systems here. >> >> I wouldn't have thought ftp would add any burden - the files have been >> generated already and it's just reading them. >> >> As you say, it is a bit odd. >> >> [...] -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
