Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
"Andy Kent" — — source: Informix-list mailing list archive (1991-1998)
If I were you I'd try to spread out over more separate disks/ arrays. A
lot depends on your application but if it's write-intensive the
bottleneck will probably be in the logs. My current preference is to have
the physical log on one disk, odd-numbered logical logs on another and
even-numbered logical logs on a third. Tables are then spread across
these. (The idea of splitting LLs in an odd way like this came from a
particularly log-hammered system where it appeared that log writes and
continuous backup were in contention with one another).
If it's read-intensive then the objective should be to spread table read
load as evenly as possible.
Not sure why you want to give the Informix code a drive to itself, surely
this will be one of the quietest areas of all?
Do report back your results won't you.
akent@cix.compulink.co.uk (Andy Kent)
------------------------------------------------
Freelance Informix Database Specialist,
Redland, Bristol, England
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.