RE: SQL performance with Local journalling -- MIDRANGE-L

× 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.

Hi John

You first statement is spot on. The SQL statement is nothing more than a statement run on a dev box to see what the raw impact of journalling was.

I was just curious as to what might have influenced the apparent journalling anomaly. I have a few thoughts (nothing specific) but I'll keep watching :)

Regards
Evan Harris

At 08:54 a.m. 24/02/2005, you wrote:

- First and foremost: Is the SQL statement typical of the workload they
run?  If not, then the performance impact of journalling the SQL
statement doesn't matter.  The ONLY thing that matters is journalling's
impact on their typical workload.
- How tuned is the system in terms of memory pools, cache, etc.?
- How many disk arms & what kind of controllers are at work?
- Any RAID or mirroring?
- Is the journal going to a separate ASP?
- How balanced is the disk usage (see STRASPBAL)?

I'm sure there are several other factors but these sprang to mind pretty
quickly.


John A. Jones, CISSP
Americas Information Security Officer
Jones Lang LaSalle, Inc.
V: +1-630-455-2787  F: +1-312-601-1782
john.jones@xxxxxxxxxx

This mailing list archive is Copyright 1997-2025 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.