RES: ER performance
Posted in 2004
I'm considering it more than ever now. I was planning to do such thing to
avoid the limitation of use HDR + ER.
While I'm planning that, is there something I could do to at least improve
performance a little?
Thanks,
Julio
-----Mensagem original-----
De: Madison Pruet [mailto:mpruet@comcast.net]
Enviada em: quarta-feira, 28 de janeiro de 2004 20:02
Para: Julio Cesar
Assunto: Re: ER performance
There's been a huge amount of work done on ER since the 7.31 days. And a
huge amount of the work has been focused on performance.
7.31 does not have nearly the parallelism with ER as 9.3+ and the queue
spooling treatment has been significantly improved. Both of these changes
will impact performance as well as use current resources much more
efficiently. Have you considered migration to 9.4?
M.P.
"Julio Cesar" <julio@prodesmaq.com.br> wrote in message
news:bv96qe$2q9$1@terabinaries.xmission.com...
>
> This is a multi-part message in MIME format.
>
> ------=_NextPart_000_0001_01C3E5CA.48A6EEC0
> Content-Type: text/plain;
> charset="Windows-1252"
> Content-Transfer-Encoding: quoted-printable
>
> Informix 7.31UD1
> Linux (Redhat 8.0)
>
> On two servers:=20
> DELL Poweredge 2650 Intel Xeon 2,8 (w/ 2 CPUs each), 2GB RAM each.
>
> My onconfig is attached to this message.
>
> Thanks
>
> -----Mensagem original-----
> De: Madison Pruet [mailto:mpruet@comcast.net]=20
> Enviada em: quarta-feira, 28 de janeiro de 2004 17:49
> Para: Julio Cesar
> Assunto: Re: ER performance
>
> Version???
>
> Configuration???
>
>
> "Julio Cesar" <julio@prodesmaq.com.br> wrote in message
> news:bv939u$10l$1@terabinaries.xmission.com...
> >
> > Hi guys,
> > A few weeks ago I got ER working on two servers between my companies.
> Since
> > that, I'm experiencing a lot of performance issues that I'd never =
> passed
> > through before.
> > The replication is working pretty fine but the server is completely
> > overloaded.
> >
> > I think I've checked out everything, although I couldn't find out what
> might
> > be happening. I just notice that cpu vps are getting overloaded =
> according
> a
> > "onstat -g glo" output. Also, locks on tables are taking longer than =
> ever
> to
> > be released.
> >
> > What should I check to solve that?
> >
> > ----
> > By the way, I have DELL Servers with 2 Intel XEON processors, with
> > Hyperthreading enabled. On Linux, the system recognize 4 processors
> ('cause
> > of hyperthreading). With that, should I use 2 or 4 CPU Vps? What's =
> better?
> > ---
> >
> > PS: I did a test, turning off all the 1500 replicates and the systems =
> got
> > faster as it they were before.
> >
> > Thanks in advance,
> > Julio
> >
> > ---
> > Outgoing mail is certified Virus Free.
> > Checked by AVG anti-virus system (http://www.grisoft.com).
> > Version: 6.0.568 / Virus Database: 359 - Release Date: 26/1/2004
> >
> >
> >
> > sending to informix-list
>
>
>
> ---
> Incoming mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.568 / Virus Database: 359 - Release Date: 26/1/2004
> =20
>
> ---
> Outgoing mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.568 / Virus Database: 359 - Release Date: 26/1/2004
> =20
> =20
>
> ------=_NextPart_000_0001_01C3E5CA.48A6EEC0
> Content-Type: application/octet-stream;
> name="onconfig"
> Content-Transfer-Encoding: quoted-printable
> Content-Disposition: attachment;
> filename="onconfig"
>
> =0A=
> Informix Dynamic Server Version 7.31.UD1 -- On-Line -- Up 2 days =
> 05:26:50 -- 1019684 Kbytes=0A=
> =0A=
> Configuration File: /opt/informix/etc/onconfig_db_pri=0A=
> #************************************************************************=
> **=0A=
> #=0A=
> # INFORMIX SOFTWARE, INC.=0A=
> #=0A=
> # Title: onconfig.prodesmaq=0A=
> # Description: Informix Dynamic Server Configuration Parameters=0A=
> #=0A=
> #************************************************************************=
> **=0A=
> =0A=
> # Root Dbspace Configuration=0A=
> =0A=
> ROOTNAME rootdbs # Root dbspace name=0A=
> ROOTPATH /mnt/informix_raw/rootdbs_1 =0A=> # Path for device containing root
dbspace=0A=
> ROOTOFFSET 0 # Offset of root dbspace into device =
> (Kbytes)=0A=
> ROOTSIZE 1024000 # Size of root dbspace (Kbytes)=0A=
> =0A=> # Disk Mirroring Configuration Parameters=0A=
> =0A=
> MIRROR 0 # Mirroring flag (Yes =3D 1, No =3D 0)=0A=
> MIRRORPATH # Path for device containing mirrored =
> root=0A=
> MIRROROFFSET 0 # Offset into mirrored device (Kbytes)=0A=
> =0A=> # Physical Log Configuration=0A=
> =0A=
> PHYSDBS rootdbs # Location (dbspace) of physical log=0A=
> PHYSFILE 65536 # Physical log file size (Kbytes)=0A=
> =0A=> # Logical Log Configuration=0A=
> =0A=
> LOGFILES 15 # Number of logical log files=0A=
> LOGSIZE 65536 # Logical log size (Kbytes)=0A=
> =0A=
> # Diagnostics=0A=
> =0A=> MSGPATH /var/log/informix_online.log # System message log file =
> path=0A=
> CONSOLE /dev/console # System console message path=0A=
> ALARMPROGRAM /opt/informix/etc/log_full.sh # Alarm program path=0A=> SYSALARMPROGRAM /opt/informix/etc/evidence.sh # System Alarm program
path=0A=
> TBLSPACE_STATS 1 =0A=
> =0A=> # System Archive Tape Device=0A=
> =0A=
> TAPEDEV /mnt/informix_backup/archive/archive_backup # Tape =
> device path =0A=
> # TAPEDEV /dev/null =0A=
> TAPEBLK 1024 # Tape block size (Kbytes)=0A=
> TAPESIZE 2048000 # Maximum amount of data to put on tape =
> (Kbytes)=0A=
> =0A=
> # Log Archive Tape Device=0A=
> =0A=
> LTAPEDEV /mnt/informix_backup/logical-logs/logical-logs_backup =0A=
> # LTAPEDEV /dev/null # Log tape device path=0A=
> LTAPEBLK 1024 # Log tape block size (Kbytes)=0A=
> LTAPESIZE 2048000 # Max amount of data to put on log tape =
> (Kbytes)=0A=
> =0A=
> # Optical=0A=
> =0A=> STAGEBLOB # Informix Dynamic Server/Optical =
> staging area=0A=
> =0A=
> # System Configuration=0A=
> =0A=
> SERVERNUM 0 # Unique id corresponding to a Dynamic =
> Server instance=0A=
> DBSERVERNAME informix_db_pri # Name database server=0A=
> DBSERVERALIASES informix_pri_local =0A=
> # List of alternate dbservernames=0A=
> DEADLOCK_TIMEOUT 60 # Max time to wait of lock in =
> distributed env.=0A=
> RESIDENT 1 # Forced residency flag (Yes =3D 1, No =
> =3D 0)=0A=
> MULTIPROCESSOR 1 # 0 for single-p