Rafi Sadowsky wrote: > > [on syslog performance and delayed writes] > Wouldn't you agree that benchmarking the effect on Disk I/O is at > least as relevant as the effect on the CPU ?
If this box did a lot more than receive syslogs -- yes, it would be relevant. However, an overloaded disk i/o bus results in the the disk i/o calls blocking, which results in higher CPU, so in the simple case, low CPU == no real problem with disk i/o. And 1GB per day isn't a problem for _any_ modern disk. Heck, even floppy can save about 1MB a minute, and there are 1440 minutes per day, so even assuming a disk as slow as a floppy, you should still be able to receive more than 100 syslog entries per second. (Although in _that_ case, you _would_ see high CPU loads ;)) -- Mikael Olsson, Clavister AB Storgatan 12, Box 393, SE-891 28 �RNSK�LDSVIK, Sweden Phone: +46 (0)660 29 92 00 Mobile: +46 (0)70 26 222 05 Fax: +46 (0)660 122 50 WWW: http://www.clavister.com _______________________________________________ Firewalls mailing list [EMAIL PROTECTED] For Account Management (unsubscribe, get/change password, etc) Please go to: http://lists.gnac.net/mailman/listinfo/firewalls
