1 / 12

RDB Issues at SLAC

The new collaboration archiver resolves previous issues with Oracle and promises increased functionality. Discover how Oracle's partitioning feature and heavily indexed tables significantly improve performance. Explore recent work in EPICS supporting RDB and the challenges faced in legacy installations.

walterweaver
Download Presentation

RDB Issues at SLAC

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. RDB Issues at SLAC Archiver Store General EPICS Support

  2. Oracle Archiver data store • Oracle 9 based • Used partitioning feature • This year’s bill $30,000 (for this feature) • New collaboration archiver has now fixed the problems we solved with Oracle • New collaboration archiver promises much more functionality soon; strong team at work here. • Oracle is MUCH slower at retrieval

  3. Oracle vs. File-basedRetrieval

  4. Why is Oracle so bad? • Heavily indexed • Partitioning improved performance x2 • Simple tables • Data not organized well with respect to minimizing number of disk reads in Oracle. • Oracle archiver with few PVs works much faster (fewer disk reads).

  5. RDB supporting EPICS • Very hot area of interest • Many talks in last several EPICS meetings • Split between “as-is” (reactive) and “generating” (proactive) RDB • Collaborations (or collaboration wishes) are strong • Issues include scope, data capture, tools - pretty much everything.

  6. Recent Work(Which I remember) • Diamond (big plans) • SNS • Argonne • BESSY • DESY • TJNAF • SPEAR

  7. EPICS Schema contains(Diamond Talk) • Domain, Subdomain, Technical Area, Component • Crate • Device • IOC • DBD • DBGroups • DB File • DB file Templates • Slot • Carrier & IP Cards • Connection Between the Cards & the Device

  8. SLAC’s long-standing idea • “UPV” Universal PV database • Generation type • Support many subsystems • Alarm handler configs • Channel watcher configs • Archiver configs • EPICS .db and .template files • NOT device oriented • NOT including cabling, maintenance, etc.

  9. SLAC prototyping(J. Rock) • Oracle developer ER diagrams • Scripts to expand EPICS db templates • Experimentation with tools for maintenance • Mass modifications • Grouped modifications • Single modifications • Experimentation with scripts for generating subsystem configs (and .db)

  10. SPEAR(S. Allison) • PV information gathered upon reboot(triggered from IOC) • Database is NOT Oracle • TCP server on host for transfer • Does data restore too • Database User Interface is php • ODBC interface for Excel export

  11. Tools • Pre-Java oracle tools (webforms, etc.) • JDeveloper • JDBC • PHP, Apache servers • Excel interfaces

  12. Biggest problem with RDB • Projects always start WAY TOO LATE with the RDB support part • The bigger the planned scope (Include maintenance? Include wiring? Include fieldbus connections?) the more important an early start is. • Can the SNS/Argonne/?? Collaboration help us “legacy installations” catch up?

More Related