09-24-2014
Hi Gacanepa,
You don't really provide enough information about the actual makeup of the disks, what is the actual backend you are using as this can make a significant difference. How are the devices accessed - there are a shedload more questions on this front.
In general and it is a generalisation the RAID10 (striped then mirrored) should provide the better performance (true also for RAID01) than RAID1. But it is not really possible to comment further than that without knowing a bit more information about your setup.
Regards
Dave
8 More Discussions You Might Find Interesting
1. Debian
I am having some troubles with apt-get. I did an apt-get update and an apt-get upgrade. Some dependencies did not download, and so I had to do `apt-get -f install` to fix that. The thing is I get an error about /var/lib/dpkg/available
root@hayek:~# apt-get -f install
Reading package lists...... (3 Replies)
Discussion started by: John Tate
3 Replies
2. Shell Programming and Scripting
Hi folks,
I am self-learning as I can
I have a script that has read a file into an array.
I can read out each line in the array with the code:
for INDEX in {0..$LENGTH} ## $LENGTH was determined at the read in
do
echo "${data}"
done
What I need to do is test the first char... (2 Replies)
Discussion started by: Marc G
2 Replies
3. Shell Programming and Scripting
Hi all,
I am looking for a quick/short way in awk to check if an associative array has any content.
I know I can split() it to an indexed array and check if the 1st element is set, or cycle through it with something like for( ele in arr ), but I want to avoid that, as I am looking for a shorter... (3 Replies)
Discussion started by: zaxxon
3 Replies
4. Linux
Hi everyone,
I am trying to prevent the ehci_hcd kernel module to load at boot time.
Here's what I've tried so far:
1) Add the following line to /etc/modprobe.d/blacklist.conf (as suggested here):
2) Blacklisted the module by adding the following string to
3) Tried to blacklist the module... (0 Replies)
Discussion started by: gacanepa
0 Replies
5. Shell Programming and Scripting
Hi,
another little question...
"sn" is an array whose elements can vary from about 55,000 to about 150,000 elements. Each element consists of an integer between 0-255, eg: ${sn} contain the value: 103 . For a decrypt-procedure I need scroll all the elements 4 or 5 times. Here is an example of... (15 Replies)
Discussion started by: math4
15 Replies
6. HP-UX
Hi Folks,
Could anyone please assist me with the what could be the scenarios to test the file system mount/umount performance check in HPUX.
Thanks in advance,
Vaishey (5 Replies)
Discussion started by: Vaishey
5 Replies
7. AIX
Hello,
P7 machine
PCI Express x8 Planar 3Gb SAS Adapter
RAID10 array(2 disks)(not AIX lvm) was configured and working, then one disk failed and IBM support replaced that. Now raid array is degraded, data is not lost. I see new disk model(same as original) serial and etc.
What I did trying... (0 Replies)
Discussion started by: vilius
0 Replies
8. Shell Programming and Scripting
Ya, I know, who in this day and age is mirroring rootvg...?
But yes, my shop does and I need to script checking for it.
I also know I could just inverse the the logic and call the LV mirrored
if the LPs and PPs were not equal. But I want to do the math in the if test
and also know I could... (5 Replies)
Discussion started by: gtsonoma
5 Replies
LEARN ABOUT REDHAT
prepare
PREPARE(7) SQL Commands PREPARE(7)
NAME
PREPARE - create a prepared query
SYNOPSIS
PREPARE plan_name [ (datatype [, ...] ) ] AS query
INPUTS
plan_name
An arbitrary name given to this particular prepared query. It must be unique within a single session, and is used to execute or
remove a previously prepared query.
datatype
The data-type of a parameter to the prepared query. To refer to the parameters in the prepared query itself, use $1, $2, etc.
OUTPUTS
PREPARE
The query has been prepared successfully.
DESCRIPTION
PREPARE creates a prepared query. A prepared query is a server-side object that can be used to optimize performance. When the PREPARE
statement is executed, the specified query is parsed, rewritten, and planned. When a subsequent EXECUTE statement is issued, the prepared
query need only be executed. Thus, the parsing, rewriting, and planning stages are only performed once, instead of every time the query is
executed.
Prepared queries can take parameters: values that are substituted into the query when it is executed. To specify the parameters to a pre-
pared query, include a list of data-types with the PREPARE statement. In the query itself, you can refer to the parameters by position
using $1, $2, etc. When executing the query, specify the actual values for these parameters in the EXECUTE statement -- refer to EXECUTE
[execute(7)] for more information.
Prepared queries are stored locally (in the current backend), and only exist for the duration of the current database session. When the
client exits, the prepared query is forgotten, and so it must be re-created before being used again. This also means that a single prepared
query cannot be used by multiple simultaneous database clients; however, each client can create their own prepared query to use.
Prepared queries have the largest performance advantage when a single backend is being used to execute a large number of similar queries.
The performance difference will be particularly significant if the queries are complex to plan or rewrite. For example, if the query
involves a join of many tables or requires the application of several rules. If the query is relatively simple to plan and rewrite but rel-
atively expensive to execute, the performance advantage of prepared queries will be less noticeable.
NOTES
In some situations, the query plan produced by PostgreSQL for a prepared query may be inferior to the plan produced if the query were sub-
mitted and executed normally. This is because when the query is planned (and the optimizer attempts to determine the optimal query plan),
the actual values of any parameters specified in the query are unavailable. PostgreSQL collects statistics on the distribution of data in
the table, and can use constant values in a query to make guesses about the likely result of executing the query. Since this data is
unavailable when planning prepared queries with parameters, the chosen plan may be sub-optimal.
For more information on query planning and the statistics collected by PostgreSQL for query optimization purposes, see the ANALYZE [ana-
lyze(7)] documentation.
COMPATIBILITY
SQL92
SQL92 includes a PREPARE statement, but it is only for use in embedded SQL clients. The PREPARE statement implemented by PostgreSQL also
uses a somewhat different syntax.
SQL - Language Statements 2002-11-22 PREPARE(7)