IBM Software Group / DB2 Information Management © 2004 IBM Corporation Informix on Linux and A...

IBM Software Group / DB2 Information Management

© 2004 IBM Corporation

Informix on Linux and A “Sneak Peek” at the New IDS Next Installer

Jerry Keesee, Director of the Informix labSandor Szabo, Development, Informix R&D, MunichKozhikode Venugopalan (Venu), Architect, Informix R&D Srini Bhagavan, Architect, IBM Data Management



Informix on Linux

Sandor Szabo, Development, Informix R&D, Munich Kozhikode Venugopalan (Venu), Architect, Informix R&D


© 2004 IBM Corporation3 © IBM Corporation 2004

Agenda

IBM Informix and LINUX

Performance & Scalability

Tips and Tricks !

Usage Trend

Strategy and Roadmap

Summary



History

1998 : IBM Informix ESQL/C& SE on LINUX

1998 : First commercial Enterprise LINUX DB – IBM IDS 7.24

1999 : LINUX edition – IBMIDS 7.30. Limited features. 4GL& I-SQL clients.

1999 : LINUX edition – IBMIDS 9.20. Full feature setsupport.

2003 : IBM IDS 9.4 - 64 bit DB Engine on zSeries

2004 : IBM IDS 9.4 64 bit on Itanium



2004 Achievements & near future plans

Reintroducing RPM support from IDS 9.40.UC5

Certification of IDS products on Red Hat & SUSE enterprise versions

Test suites to vendors

Time limited license support

Support for ALL IBM platforms that support LINUX !!

IA64 (64-bit edition for Intel Itanium based systems)

POWER™ 64-bit (IBM eServer™ iSeries™ and pSeries® systems)

AMD64 (64-bit edition for AMD Opteron and Athlon64 based systems)

Intel® EM64T



2004 Achievements & near future plans

Exploitation of the 2.6 kernel

KAIO support

Processor Affinity to achieve improved scalability

SNMP support



Current HW support on Linux

Support for 32 bit Intel x86 platforms (32-bit edition for Intel Pentium®, Xeon and AMD Athlon )

zSeries® 64 bit (IBM eServer zSeries systems)

IA64 (64-bit edition for Intel Itanium based systems)

POWER™ on Linux (IBM eServer™ iSeries™ and pSeries® systems) supported with IDS vNext

AMD 64 & EM64T supported with IDS vNext



IBM Informix leverage

Leveraging IBM relationships & partnerships with Linux vendors like SUSE, Red Hat (Better escalation channel for issues).

Access to alpha/beta versions of Linux distributions

Beta program participation

Supply test suites to Linux distributors

Share IBM Linux strategy vision

Easier access to new hardware

Translates as benefits to our customers!



Agenda



Tips and Tricks !

Usage Trend


Summary



Performance Tips

Scales linearly on SMP – internal benchmarks

Up to 2.5GB of contiguous shared memory (32 Bit)

Very Large Memory > 4 GB support (64 Bit)

Large file suport > 2G in 9.4 (>7.25, SE and CISAM)

Choose your FS carefully for cooked files



Scalability & Performance improvements

Choose PAGE size carefully in IDS vNext

Processor Affinity

KAIO (on raw devices)



IDS 9.4 for Linux on zSeries

IBM Informix 9.40 is the first IBM database engine to fully exploit the large memory, 64-bit capabilities of the Linux kernel on the zSeries.

Fully implemented 64-bit architecture

64-bit systems reduce the work of the application programmer by removing the design constraints inherent in 31-bit architectures



Objectives of the sizing project

Analyze the performance of the Informix database by scaling CPUs, memory and database size

Identify the scalability of Linux for IBM zSeries using Informix transactional workloads

Investigate the performance of different disks

The test environment is a customer-like environment, not a system for high-end benchmarking.



Workloads used.....

TPC-C like

• High hit ratio: use a small number of warehouses (10 or 20) and stay with this through CPU and memory scaling

• Low hit ratio: scale number of warehouses with throughput while scaling CPUs and memory. The ratio between warehouses and new order transactions per minute is 1:12.



CPU Scaling [2GB workload fully cached – 10WH]



""The workload scales perfectly from 1 to 16 CPUs, The workload scales perfectly from 1 to 16 CPUs, demonstrating that thedemonstrating that the

Informix database, SUSE SLES8 and the zSeries Informix database, SUSE SLES8 and the zSeries hardware are very well suited for scalinghardware are very well suited for scaling

even beyond 4 CPUseven beyond 4 CPUs""

""The workload scales perfectly from 1 to 16 CPUs, The workload scales perfectly from 1 to 16 CPUs, demonstrating that thedemonstrating that the

Informix database, SUSE SLES8 and the zSeries Informix database, SUSE SLES8 and the zSeries hardware are very well suited for scalinghardware are very well suited for scaling

even beyond 4 CPUseven beyond 4 CPUs""

Large Scale Linux Solution Test CenterLarge Scale Linux Solution Test CenterInformix 9.4.0 FC3 onInformix 9.4.0 FC3 on

SUSE LINUX ENTERPRISE SERVER 8 SP2 (64-bit)SUSE LINUX ENTERPRISE SERVER 8 SP2 (64-bit)on IBM zSerieson IBM zSeries

Large Scale Linux Solution Test CenterLarge Scale Linux Solution Test CenterInformix 9.4.0 FC3 onInformix 9.4.0 FC3 on

SUSE LINUX ENTERPRISE SERVER 8 SP2 (64-bit)SUSE LINUX ENTERPRISE SERVER 8 SP2 (64-bit)on IBM zSerieson IBM zSeries



Agenda



Tips and Tricks !

Usage Trends


Summary



Tips and Tricks

LibAIO.so library – OS requirement

minimum version is libaio 0.3.96-3.

KAIO automatically works on raw devices and can be turned off by KAIOOFF=1

Processor affinity onconfig variables

• AFF_SPROC = <Start Processor>

• AFF_NPROCS = <# Processors>



Tips and Tricks

AS (Anticipatory I/O)

NOOP (No-op I/O)

CFQ (Complete Fairness Queueing )

DEADLINE

Experiences with different

2.6 Kernel I/O schedulers on zLinux



How to Change the Location of Shared Library for a Process on SUSE Linux……

Beginning with kernel version 2.4.19, Linux provides a way to dynamically change the default start address for shared libraries on a per-process basis. This feature is available, if the file /proc/$$/mapped_base exists.

To change the start address for shared libraries of the oninit processes, the new start address needs to be specified by user root in the shell from where oninit is started.



Example:$ echo $$29712$ su rootPassword:# # the following sets the start address of shared libraries to

0xB0000000:# echo -1342177280 > /proc/29712/mapped_base# exit$ oninit

Assuming the $ONCONFIG parameter SHMBASE is 0x10000000, this gives 2.5 GB of contiguous address space available for the database server.

How to Change the Location of Shared Library for a Process on SUSE Linux……



How to Change the Location of Shared Library for a Process on RedHat Linux……

On Red Hat Enterprise Linux 3 the start address for shared libraries is 0xb7600000 and memory address space is utilized downwards.

The ONCONFIG variable SHMBASE is recommend to be set at SHMBASE 0x10000000L

- $ cat /proc/25830/maps [see notes]



LINUX file systems

EXT2 is good ….

JFS gave very good performance in our tests

Reiser File System (reiserfs), which is the default file system on some Linux distributions gives bad performance....

Lots of memory is good for file system caching!!



Agenda



Tips and Tricks !

Usage Trend


Summary



Informix Success Stories on Linux

Cisco: voice over IP as embedded DB

Italian Foreign Ministry: 200 embassies world wide

GE Interlogix: world´s largest access-control system supplier

Online Computing: ERP supplier for Fireworks companies

CornerCap: Portfolio management a

Physics Institute of University of Cantabria: GRID research



Informix Success Stories on Linux

Apropos Retail: Management system for retailers

French Air Force: Human Resource Department

Magna Steyr Fahrzeugtechnik

Morgan Stanley: Financial Datablade and Real-time Loader

Sabo Italy: Fire fighting liquids, products for cosmetic industry



Reference Customers on Linux zSeries

T-Systems International GmbH

Bayersiches Landesamt fuer Statistik und Datenverarbeitung

State of California

Datenzentrale Mecklenburg-Vorpommern

China Life and PICC

All quotes from published success stories or referencesSee the success story section off of http://www.ibm.com/software/data/informix or talk to your sales rep for more details



Flexibility, Options, Efficiency Reduced Costs!

Secretaria de Finanzas Gobierno del Estado de

Jalisco

IDS + WebSphere

Web-based tax collection system

Needs: resiliency, 24x7 availability, ease of use, open standards

Solution:– Web portal based based on IBM WebSphere Application Server on Linux– IBM Informix Dynamic Server– IBM Informix SQL, ESQL/C, MaxConnect

Value:– Significant cost reduction– More efficient tax collection– Convenience and speed lead to increased customer satisfaction– Current solution allows for future expansion



El Salvador Tax Administration Office

Characteristic Original Server Production Server

RDBMS ODS 7.31 FC2 IDS 9.4 UC2

Avg Client Connections 360 500

Response Time Data Entry - 50% faster

Base Tax Report 15 minutes 5 minutes

1/3 of the time

Declaration Posting 7 hours 3 hours

<1/2 of the time

Processing Tax Forms 4 hours 40 mins

<1/6 of the time

Processing EDA 3 hours 60 mins

1/3 of the time

Comparison Statistics



Agenda



Tips and Tricks !

Usage Trend


Summary



LINUX Strategy

Overall IBM strategy and not just DM!

Support for enterprise versions of Redhat and SUSE

Other versions evaluated purely based on business needs

Support the 2.6 Kernel +

Support for newer glibc versions

GOAL: Certify on enterprise [Red Hat & SUSE] within 90 days of GA



Linux Intel x86 SupportProduct SUSE SLES 8 / UL 1.0 SUSE SLES 9 RHEL 3 RHEL 4

IDS 9.40 (UC5) (UC4) Planned

IDS vNext Planned Planned Planned

CSDK 2.81 (UC3)

CSDK vNext Planned Planned Planned

4GL 7.32 Planned (UC2) Planned

C-ISAM 7.26 Planned Planned

SE Planned Planned

Online 5.2 Planned Planned



Linux zSeries (64-Bit) Support

Product SUSE SLES 8 / UL 1.0 SUSE SLES 9 RHEL 3 RHEL 4

IDS 9.40 (FC5) (FC5) Planned


CSDK 2.81


4GL 7.32 Planned Planned Planned



Linux Itanium (64-Bit) Support


IDS 9.40 Planned (FC3) Planned


CSDK 2.81 (FC3)




Linux pSeries/iSeries (64-Bit) Support


IDS vNext No Planned Planned Planned

CSDK vNext No Planned Planned Planned

4GL 7.32 No Planned Planned Planned



Linux AMD64 (32-Bit) Support

Product SUSE SLES 9 RHEL 3 RHEL 4





Agenda



Tips and Tricks !

Usage Trend


Summary



Summary

IDS is continually evolving to exploit Linux features for best performance

Similarly, tuning practices are very portable across IDS platforms, but an understanding of Linux gives more opportunities

Linux is maturing as a platform for the enterprise– Consolidation of major distributions is occurring, but very vigorous open-

source development continues– Tools to enable deployment are more available & robust

There are strong performance advantages to moving to a recent kernel

Adoption rates for IBM Informix on Linux increase

LINUX is unique … lets put it to work!



External Website for Informix Linux Information

www.ibm.com/informix/linux



Sneak peek at the new IDS vNext Installer

Srini Bhagavan Architect, IBM Data Management



Agenda

The new Installer

What is changing?

How will it benefit me?

Installation options

Screen shots



IDS vNext Install Platform choice

Embedded requirement

Product integration with IBM offerings like IR, ISV product bundling advantages, etc.,

Autonomic Improvements

Uniform interface across all UNIX platforms

GUI based install capability

Permissions - entire installation is run as a single user instead of combination

Silent install capability



IDS vNext Install Platform choice

Uninstall capability

Helps achieve uniform installation across IBM product portfolio. Same look and feel for our customer base regardless of the product.

Helps us set the stage for a single install & deployment across DM at some point.

Enhanced error reporting - dynamic in many cases. Errors are reported up-front and prevents the need to deal with debris.

Minimizes critical manual steps required prior to installation

Usability enhancements

Experienced user support



Script Vs Java/ISMP Installer – A Comparison

1. Getting Started…

The product usually delivered as a tar ball, had components tar’d twice.

An user extracts it once, only to find another tar ball which has to be extracted again.

The ISMP based product is also a tar ball.

An user extracts it once, instead of getting another tar ball, ends up with a jar file not requiring an additional step of extraction.




2. Installing the Product…

The product is not provided in extracted form in the Media.

The user has to either copy or extract to a local file system to install the product.

Only TUI mode of installation was supported.

The installer has the capability to be started from the Media. No local extraction is required

The installer support GUI, TUI and Silent modes of installation

GUI: Graphical User Interface

TUI: Text User Interface (also referred to as console mode).




3. Product Requirements…

Lots of Disk Space was needed for performing various activities (to the tune of 1.5GB)

Some portion of installation has to be run as one user and another portion as root user.

Media size reduced anywhere from 30-50% making the product less Bulky

Start to finish only with one user id and all the steps required for the installation are taken care of




4. Audience – opening doors to Novice users…

A person with very less expertise doing product installation will have to understand the product structure to get started with installation.

User has to start all over again, if some problem happens during installation.

On a side note, licensing (SEL) was external and visible.

A person with very less expertise doing product installation can install the product

The Installer drives the user by getting the required information

Licensing is embedded into the product




5. Eliminate Manual Steps…

User had to define, environment variables based on their setup ($INFORMIXDIR, $ROLE_SEP etc.,)

Possible problems with file permission with extraction of source files.

The installer accepts information dynamically, eliminating the need for preset values in the environment

A single user based installation performs all the required tasks and the product is setup properly at the destination



vNext Installer Options

1. Current Installer can be invoked by the following methods

2. installserver [preferred] Uses bundled JVM, if JAVA not found in the PATH

3. Installserver –javahome [for users that want to use a local java]

4. Java –cp IIF.jar run [for users who want to invoke directly – advanced]

5. Installserver –legacy [extracts a legacy distribution]



Installer Options

Additionally on LINUX also package the following RPMs [since 9.40.UC5]

• Product.rpm• GLS.rpm• Message.rpm

LINUX users have a choice to use this option and its details are documented in users guide

For enhanced usability, a wrapper script is provided that invokes the RPMs in the correct sequence



vNext Installer Screen Shots



Splash screen



GUI Welcome Screen



License Panel



Install Destination



Product choices – All or Specific components



GUI Role Separation



GUI Summary Panel



GUI Installation Progress



GUI Installation Complete



Console Screen shots



License Agreement



Console Product Uninstall



Key take aways

Java based Installer using ISMP

Eliminated all the critical manual steps

Simple to use compared to previous installer

GUI based Installer in addition to console mode

Silent install support

Uninstaller capability

Legacy install extraction option to support advanced users



http://www.ibm.com/software/data/informix

IBM Software Group / DB2 Information Management © 2004 IBM Corporation Informix on Linux and A...

Documents

Transcript of IBM Software Group / DB2 Information Management © 2004 IBM Corporation Informix on Linux and A...