1 Alice DAQ Configuration DB [email protected].

1

Alice DAQConfiguration DB

[email protected]

mailto:[email protected]

231/01/2007 – S.C. Alice DAQ configuration DB

ALICE DAQ Architecture

GDC GDCGDCGDC

CTP

LTU

TTC

FERO FERO

LTU

TTC

FERO FERO

LDCLDC

BUSY BUSY

Rare/All

Storage Network

TDS

343 DDL

EDM

LDCLoad Bal.

LDC LDC

HLT Farm

FEPFEP

DDL

H-RORC

10 DDL

10 D-RORC

10 HLT LDC

163 DDL

TDS

DS DS

Event-Building Network

425 D-RORC

50 GDC 10 DS

PDS

25 TDS

200 Detector LDC

EventFragment

Sub event

Event

File


ALICE DAQ Architecture

GDC GDCGDCGDC

CTP

LTU

TTC

FERO FERO

LTU

TTC

FERO FERO

LDCLDC

Storage Network

TDS

EDM

LDC LDC LDC

HLT Farm

FEPFEP

TDS

DS DS

Event-Building Network

PDS

Trigger High-Level Trigger

Detectors

Data Acquisition


DATE v4 - configuration• DATE Configuration stored in ASCII files

– $DATE_SITE_CONFIG– Shared by NFS

• DATE DB package used to read static information:– roles (who is what) …– detectors (what detectors and sub-detectors are made of) …– triggers (what is activated by each trigger) …– event building (what to do with the events on GDCs) …– memory banks (where to store the data structures)

• Readout equipment (data sources on LDCs)

• RunControl parameters (dynamic)

• Misc. items: DIM DNS, environment, …

2004


DATE v5 - configuration

• SQL based• Constraints to avoid inconsistencies• GUI• APIs unchanged• Backward compatible (runtime/compile switch)

• Critical shared resources distributed with SQL• Few static items still in flat files

2005

2007: Now everything in MySQL


Operator console MySQLserver

DATE nodes

Architecture


SQL db

• Improves data distribution and configuration integrity compared to NFS ASCII files.

• Simple structure, few tables (10s), little data (1000s records)

• Peak read access when DAQ starts (100s clients)

• Infrequent write access (by operator and runcontrol)• No use of special features, standard SQL, any back-end

should fit• DATE Language interfaces: C, Tcl/Tk, php


Config db schema


SQL db - requirements

• Ease of installation– Dynamic setup, may need to create many

times different systems– Independency for quick changes

• Control on the server:– to monitor behavior– how to tune performance– improve server setup accordingly

for development phasefor development phase


SQL db - requirements

• Version control– Version must be stable during data taking period

• Maintenance and operation– Fast reactivity, known procedures, internal know-how– On the fly setup change when needed (performance

tuning, …)

for production phasefor production phase


MySQL• Open source• Free DB system to distribute to institutes using DATE• Easy setup• Good feedback on bugs (#7838)• Platform compatibility• Interfaces for C, Tcl, Php …• Good performance• No strong dependency, in house expertise

• MySQL version 4: innodb, …• MySQL version 5: promising features (views, triggers, …)

2005


MySQL

• RPM setup, binary tarball, source compilation• Server setup:

– Users and table creation with simple SQL commands– Can also copy an existing database: copy whole directory and it

works (good for backup as well)

• Client program: linked with corresponding platform library

Installation is a matter of minutes


DB performance tests

0 10 20 30 40

1

2

3

4

5

6

Con

nect

ions

to s

erve

r

Thousands inserts per second

2 x Opteron Dual-Core 2.2 GHz DDR 400SLC4 64bit exec



2 x Xeon 3.2 GHz DDR2 400

1 x Pentium 4 2.8 GHz DDR 400

2 x Xeon 2.4 GHz DDR 266

2 x Xeon 2.8 GHz DDR 333

(same order on plot in each group)


DB performance tests

0

50

100

150

200

250

300

15:00 15:05 15:11 15:17 15:23

Time

Number ofconnections

New (per second) Active Maximum

Operator console MySQLserver

DAQ nodes

0

50

100

150

200

250

300

15:11:31 15:11:40 15:11:48 15:11:57 15:12:06 15:12:14

New connections Active connectionsMax. number of active select queriesinsert queries (logs) / 10

Configuration DB:concurrent access65 LDC, 65 GDC


DB performance testsMySQL server load - aldaqds04 - 15 LDCs/12 GDCs SOR

0

10

20

30

40

50

60

70

80

90

100

10:5

4:17

10:5

4:22

10:5

4:25

10:5

4:30

10:5

4:37

10:5

4:43

10:5

4:48

10:5

4:52

10:5

4:55

10:5

4:58

10:5

5:01

10:5

5:04

10:5

5:10

10:5

5:15

10:5

5:22

10:5

5:29

10:5

5:34

10:5

5:37

10:5

5:43

10:5

5:49

10:5

5:55

Time

Connections in 1 second Max. simultaneous connections CPU used

2007


MySQL operation

• Excellent stability – no crash so far

• Simplicity to setup & run

• Scalable

• Nice GUI tools:– MySQL Administrator– MySQL Query Browser– MySQL Workbench


Other DB usage in Alice DAQ

• infoLoggerstore logs of all DAQ nodes

• Detector Configspecific hardware configuration

• File Exchange Serverexport data to outside world

• LogbookSummary information for each run

• Machine dbDAQ hardware configuration: LAN, cables, racks, …


Conclusion

• Now entering production• Software ready and stable• Still flexible for new features

• Good choice so far

1 Alice DAQ Configuration DB [email protected].

Documents

Transcript of 1 Alice DAQ Configuration DB [email protected].