Hello Tammy,
We started with v5 so we had two boxes for HA purposes.
Then we asked to have a smaller box for test, this was because we needed to give developer a test environment where they can be able to do whatever they need without need of controlling resources. All resources of one box are shared among all environment enabled on it, for instance space is shared among al DB2 (production/test/development) and there is no way to limit it, so we restricted the permission to add tables in the accelerator, but this isn't the way developers are used to work.
When we migrated to v7, the Db2 analytics Accelerator on Z was at its very beginning and for the amount of queries running (we have one singlet applications that runs 500 queries/sec) to have Analytics Accelerator on Integrated Analytics System was still the best choice. Since than I know it has improved a lot (especially with v7.5).
I asked once at a workshop (in October 2019) with the people from lab if there could be a reason for us to leave the stand alone box and run on Z, they told me no that for our environment since we already had the stand alone box we could continue that way. Remember in 2019 accelerator on Z was still young and has a lot improved.
I think all depends on your workload and on your assets that you already have available.
The HW resources required are CPU(IFLs), Memory, Network adapters, storage adapters, Storage. You need to make consideration on those.
Customizable configuration and highly flexible scaling
Single Node: Minimum 2 IFLs / 64 GB memory, maximum 40 IFLs / 4,096 GB
Multi Node: Minimum 30 IFLs / 1.5 TB memory, maximum 190 IFLs / 20 TB
Can utilize shared infrastructure, such as network or storage adapters
Those are the characteristics of the accelerator on Z:
•Running on IBM Z servers in a Secure Service Container (SSC) LPAR
•"Download & go" –very easy to deploy
•Delivers the full SW stack including operating system, docker engine, Db2 Warehouse engine, Accelerator components and infrastructure management
A solution leveraging IBM Z infrastructure
•Runs on IBM Z systems starting with z13 (z13, z13s, z14, z14 ZR1, z15)
•Leverage "white space" (unused capacity) in existing systems –or dedicate a stand-alone system, e.g. LinuxONE
•Leverage existing storage systems (CKD or FB) –no dedicated storage system required
•Leverage existing IBM Z high-availability and disaster recovery solution by integration of the Accelerator with GDPS/Metro
Said that you could have a mixed environment, have a test environment using an accelerator on Z.
To have it on a separate box it also means a different maintenance management.
All considerations you need to do.
Hope I have helped you with my considerations. Feel free to ask me more questions.
Regards Chiara
------------------------------
Chiara Baldan
------------------------------
Original Message:
Sent: Wed June 03, 2020 04:50 PM
From: Tammy Brodahl
Subject: Request for experiences with Db2 Analytics Accelerator for z/OS (IDAA V7)
We are planning on upgrading to Db2 Analytics Accelerator for z/OS and are wondering if anyone will share their experiences with using Db2 Analytics Accelerator for z/OS. We are trying to determine which deployment may fit best for our company, Db2 Analytics Accelerator on Z or Analytics Accelerator on Integrated Analytics System. Would anyone like to share:
- Which deployment was used, Db2 Analytics Accelerator on Z or Analytics Accelerator? And if Db2 Analytics Accelerator on Z was used, was it using IFLs on z15 or LinuxOne?
- Why did was this deployment typed used?
- Any positive/favorable experiences with the deployment selection?
- Any issues/challenges with the deployment selection?
------------------------------
Tammy Brodahl
------------------------------
#Db2forz/OS