×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
... journaling will add some I/O workload to your system, for each update operation the data has to be written two times, but it's treated as redundant data and only one of both is synchronous I/O (the record or the journal, depends on commit or not). The performance impact could be minimized by caching, or by providing a dedicated ASP for the Journalreceiver, so that there is no repositioning of disc arms for this sequential write operations.
The main factor is IMHO the balance of the system, if you have enough disc arms, there will be nearly no performance degradation (and 5 % degradation is not really measurable). One of the problems might be some boxes out with nearly as much CPUs as disc arms and heavy usage of unprotected storage (= swap for missing main memory) - her you will see maybe the numbers Charles was writing of.
D*B
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
