Date: Mon, 7 Aug 2006 16:14:50 -0300 (ADT) From: "Marc G. Fournier" <scrappy@freebsd.org> To: questions@totaldiver.net Cc: questions@freebsd.org Subject: Re: BSDstats Project v2.0 ... Message-ID: <20060807161058.P7522@ganymede.hub.org> In-Reply-To: <3631.192.168.1.30.1154943343.squirrel@Scorpio.totaldiver.net> References: <20060807003815.C7522@ganymede.hub.org> <3631.192.168.1.30.1154943343.squirrel@Scorpio.totaldiver.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 7 Aug 2006, questions@totaldiver.net wrote: > While I'm definately interested in the statistical reporting, I do have > one suggestion: > > Add a random "sleep" time to the update. > > Otherwise, the reporting server is gonna get HAMMERED once a month, > assuming this project gains any kind of momentum. > > A random sleep timer at the beginning of the script over (for example) a 3 > hour window could make the load bearable for the checkin server. Just > something to consider. To be totally honest, 'load n the checkin server' isn't something I'm terribly worried about ... right now, we are at ~200 hosts checking in, from various time zones (see http://bsdstats.hub.org/bsd_statistics.php for countries that have checked in so far) ... so, even at month end, taking into consideration time zones, I don't expect a major hit ... now, if we get to 10's of thousands of hosts, which I'd *love*, then I may worry, but by then, I'll have a Dual-Core Dual CPU server in place that I can move the whole thing over onto ... IMHO, its going to be a slow ramp up over a long period of time, but, as I mentioned earlier ... it has to start somewhere, and we've accomplished that ... now to get everyone actually checking in, now that will be a feat to see :) I've also contacted folks @ NetBSD, OpenBSD and DragonflyBSD about participating ... again, our aim is to show that the *BSD camp is a market to look at, not just a group of hobbiests ... > > >> >> I've now committed v2.0 of the 300.statistics periodic script ... this one >> adds the device reporting that we'd talked about previously, and the >> summary reports now reflect the driver(s) in use for those deciding to >> report ... >> >> This Phase of the script is optional, and not enabled by default ... I >> can't think of any reason why you wouldn't want to report it, but just in >> case someone feels it poses a problem, its an opt-in report ... >> >> pkg-message updated to reflect the extra line you need to add to >> /etc/periodic.conf: >> >> monthly_statistics_report_devices=yes >> >> I've written it to report driver + chip= information from pciconf -l, >> since even pciconf -lv doesn't seem to use card= ... the summary report >> will be extended next to show both vendor and chip statistics ... >> >> Let me know of any problems ... >> >> ---- >> Marc G. Fournier Hub.Org Networking Services >> (http://www.hub.org) >> Email . scrappy@hub.org MSN . scrappy@hub.org >> Yahoo . yscrappy Skype: hub.org ICQ . 7615664 >> _______________________________________________ >> freebsd-questions@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-questions >> To unsubscribe, send any mail to >> "freebsd-questions-unsubscribe@freebsd.org" >> > > > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" > ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . scrappy@hub.org MSN . scrappy@hub.org Yahoo . yscrappy Skype: hub.org ICQ . 7615664
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060807161058.P7522>