Обсуждение статьи: Новые серверы IBM на базе процессора POWER7

как грил Остап Бендер ... "Вас обманули. Вам дали гораздо лучший мех. Это шанхайские барсы. Ну да! Барсы! Я узнаю их по оттенку. Видите, как мех играет на солнце!"

Видео о технологии Active Memory Expansion в POWER7.

POWER7 based machines introduces the Active Memory Expansion (AME) which makes the memory of an AIX 6 Logical Partition (LPAR) seem larger than is actually is by compression memory pages on the fly. This movie covers the basics of how it works, how to switch it on at the LPAR level, running the "amepat" tool to predetermine good AME settings and its effect and then how to monitor it while its running.
For more information read the AME Whitepaper - to be released soon
http://www.ibm.com/developerworks/wikis/display/WikiPtype/Movies http://public.dhe.ibm.com/systems/power/community/aix/AIX_Movies/ActiveMemoryExpansion.wmv

Выписал SAP тесты для всех "550ых"

=== 550я POWER5+ (04.10.2005) ===========

The SAP SD standard mySAP ERP 2004 application benchmark performed on
September 13, 2005 by IBM in Beaverton, OR, USA was certified on October 4, 2005
with the following data:
Number of benchmark users & comp.: 1,000 SD (Sales & Distribution)
Average dialog response time: 1.97 seconds
Throughput:
Fully processed order line items/hour: 100,330
Dialog steps/hour: 301,000
SAPS: 5,020
Average DB request time (dia/upd): 0.026 sec / 0.075 sec
CPU utilization of central server: 99%
Operating System central server: SuSE Linux Enterprise Server 9
RDBMS: DB2 UDB 8.2.2
SAP ECC Release: 5.0
Configuration:
Central server:
IBM System p5 Model 550,
4 processors / 4 cores / 8 threads, POWER5+, 1.9 GHz,
32 KB(D) + 64 KB(I) L1 cache per processor,
1.92 MB L2 cache and 36 MB L3 cache per 2 processors,
32 GB main memory


=== 550я POWER6 (29.01.2008) =====================================

The SAP SD standard SAP ERP 6.0 (2005) application benchmark performed on January 23, 2008
by IBM in Beaverton, OR, USA was certified on January 29, 2008 with the following data:
Number of benchmark users & comp.: 3,104 SD (Sales & Distribution)
Average dialog response time: 1.91 seconds
Throughput:
Fully processed order line items / hour: 312,670
Dialog steps / hour: 938,000
SAPS: 15,630
Average DB request time (dia/upd): 0.019 sec / 0.049 sec
CPU utilization of central server: 97%
Operating System central server: Redhat Enterprise Linux 5
RDBMS: DB2 9.5
SAP ECC Release: 6.0
Configuration:
Central server:
IBM System p 550, 4 processors, 8 cores, 16 threads,
POWER6 4.2 GHz, 128 KB L1 cache and 4 MB L2 cache per core, 32 MB L3 cache per processor, 64 GB main memory




=== 550я POWER6 (16.06.2009) =====================================

The SAP Sales and Distribution (SD) Standard Application Benchmark performed on June 01, 2009,
by IBM in Beaverton, OR, USA, was certified on June 16, 2009, with the following data:
Number of SAP SD benchmark users:
3,752
Average dialog response time:
0.97 seconds
Throughput:
Fully processed order line items per hour:
410,330
Dialog steps per hour:
1,231,000
SAPS:
20,520
Average database request time (dialog/update):
0.013 sec / 0.016 sec
CPU utilization of central server:
99%
Operating system, central server:
AIX 6.1
RDBMS:
DB2 9.5
SAP Business Suite software:
SAP enhancement package 4 for SAP ERP 6.0 (Unicode)
Configuration:
Central server:
IBM System 550, 4 processors / 8 cores / 16 threads,
Power6, 5.0 GHz, 128 KB L1 cache and 4 MB L2 cache per core, 32 MB L3 cache per processor, 64 GB main memory
Certification number: 2009023
© 2009


=== 550я POWER7 (08.02.2010) в полной набивке =======================
The SAP Sales and Distribution (SD) Standard Application Benchmark performed on October 30, 2009,
by IBM in Beaverton, OR, USA, was certified on February 08, 2010, with the following data:
Number of SAP SD benchmark users:
15,600
Average dialog response time:
0.98 seconds
Throughput:
Fully processed order line items per hour:
1,704,330
Dialog steps per hour:
5,113,000
SAPS:
85,220
Average database request time (dialog/update):
0.015 sec / 0.028 sec
CPU utilization of central server:
99%
Operating system, central server:
AIX 6.1
RDBMS:
DB2 9.7
SAP Business Suite software:
SAP enhancement package 4 for SAP ERP 6.0
Configuration:
Central server:
IBM Power System 750, 4 processors / 32 cores / 128 threads,
POWER7, 3.55 GHz, 32 KB(I) + 32 KB(D) L1 cache and 256 KB L2 cache per core, 4 MB L3 cache per core, 256 GB main memory

=====================================================

Последняя конфигурация красивая, но будет стоить конечному потребителю сильно дорого для приложений, в которых софт лицензируется поядерно. Я б сказал ОЧЕНЬ дорого.

Новое железо в картинках

750:

4 Socket 4U
6 or 8 cores per socket
3.0 to 3.55 GHz
Energy-Star Qualified (first Energy Start certified RISC system)
Up to 181,000 CPW




770:

12 or 16 core 4U Nodes
Up to 4 Nodes per system
3.1 and 3.5 GHz
Capacity on Demand
Enterprise RAS
Up to 292,700 CPW




780:

New Modular High-End
Up to 64 Cores
TurboCore
3.86 or 4.14 GHz
Up to 343,050 CPW
Capacity on Demand
Enterprise RAS
24x7 Warranty
PowerCare




На последней картике обычная высокая стойка 19 дюймов ширины. Ну какой хайэнд обойдется без красивой дверки

иначе не продать.

Источник информации -> тут

Как они над дисками в 770-м издеваются-то

Кстати, логотип ИБм-ов справа вверху на стоечке 780-го всё так же приклеивается, да? И потом либо сам упадёт, либо заботливые руки помогут

а я только сейчас посмотрел rPerf. был впечатлен.

770 P7/64 3.10 GHz - 579,39 rPerf
780 P7/64 3.86 GHz - 685,09 rPerf
595 P6/64 5.00 GHz - 553,01 rPerf
http://www-03.ibm.com/systems/power/hardware/reports/system_perf.html

andrewk писал(а):

Цитата:
а я только сейчас посмотрел rPerf. был впечатлен.

770 P7/64 3.10 GHz - 579,39 rPerf
780 P7/64 3.86 GHz - 685,09 rPerf
595 P6/64 5.00 GHz - 553,01 rPerf

http://www-03.ibm.com/systems/power/hardware/reports/system_perf.html

ЛЮБАЯ однопоточная задача будет выполняться заведомо медленнее на P7 односительно аналогичной задачи, бегущей на P6.
Остальное маркетинговая брехня.
P7 машины будут интересны только для тех сред, в которых умеют эффективно утилизировать многопоточность. Я таких не знаю, ну кроме тех, на которых работает мой банк.