001024153 001__ 1024153
001024153 005__ 20241218210658.0
001024153 0247_ $$2datacite_doi$$a10.34734/FZJ-2024-01995
001024153 037__ $$aFZJ-2024-01995
001024153 041__ $$aEnglish
001024153 1001_ $$0P:(DE-Juel1)143606$$aBrömmel, Dirk$$b0$$eCorresponding author$$ufzj
001024153 1112_ $$a4th Conference for Research Software Engineering in Germany$$cWürzburg$$d2024-03-05 - 2024-03-07$$gdeRSE24$$wGermany
001024153 245__ $$aIntegrated Continuous Benchmarking
001024153 260__ $$c2024
001024153 3367_ $$033$$2EndNote$$aConference Paper
001024153 3367_ $$2DataCite$$aOther
001024153 3367_ $$2BibTeX$$aINPROCEEDINGS
001024153 3367_ $$2DRIVER$$aconferenceObject
001024153 3367_ $$2ORCID$$aLECTURE_SPEECH
001024153 3367_ $$0PUB:(DE-HGF)6$$2PUB:(DE-HGF)$$aConference Presentation$$bconf$$mconf$$s1734522152_24844$$xAfter Call
001024153 520__ $$aWhen developing research software, it is often relevant to track its performance over time. It is even vital when targeting high-performance computing (HPC). Changes to the software itself, the used toolchains, or the system setup should not compromise how fast users obtain their results. Ideally, performance or scalability should only ever increase. Hence benchmarking should be an integral part of testing, in particular for HPC codes. At the same time, up-to-date benchmarks that are publicly available can advertise the code and inform users how to set-up the software in the most ideal way or whether they are achieving the expected performance.To limit the burden on developers, the aforementioned steps should be automated within continuous integration (CI) practices, introducing continuous benchmarking (CB) to it. For HPC, an added complexity is the requirement of more than the usual CI backends, with access to longer running steps and more resources than available on a single node. Reusing test cases that are easily run by hand is another simplification for developers that may not be familiar with the research field. We show our solution to CB that we use at the Juelich Supercomputing Centre (JSC), where we combine the already implemented benchmarking via the Juelich Benchmarking Environment (JUBE) with properly authenticated CI steps running on the supercomputing systems at JSC. The combined results, including the evolution over time, are then further processed and displayed on pages published via CI.
001024153 536__ $$0G:(DE-HGF)POF4-5112$$a5112 - Cross-Domain Algorithms, Tools, Methods Labs (ATMLs) and Research Groups (POF4-511)$$cPOF4-511$$fPOF IV$$x0
001024153 536__ $$0G:(DE-Juel-1)RG-RSE$$aRGRSE - RG Research Software Engineering for HPC (RG RSE) (RG-RSE)$$cRG-RSE$$x1
001024153 7001_ $$0P:(DE-Juel1)174136$$aFritz, Jakob$$b1$$ufzj
001024153 7001_ $$0P:(DE-Juel1)132268$$aSpeck, Robert$$b2$$ufzj
001024153 8564_ $$uhttps://events.hifis.net/event/994/contributions/7948/
001024153 8564_ $$uhttps://juser.fz-juelich.de/record/1024153/files/ICB.pdf$$yOpenAccess
001024153 8564_ $$uhttps://juser.fz-juelich.de/record/1024153/files/ICB.gif?subformat=icon$$xicon$$yOpenAccess
001024153 8564_ $$uhttps://juser.fz-juelich.de/record/1024153/files/ICB.jpg?subformat=icon-1440$$xicon-1440$$yOpenAccess
001024153 8564_ $$uhttps://juser.fz-juelich.de/record/1024153/files/ICB.jpg?subformat=icon-180$$xicon-180$$yOpenAccess
001024153 8564_ $$uhttps://juser.fz-juelich.de/record/1024153/files/ICB.jpg?subformat=icon-640$$xicon-640$$yOpenAccess
001024153 909CO $$ooai:juser.fz-juelich.de:1024153$$pdriver$$pVDB$$popen_access$$popenaire
001024153 9101_ $$0I:(DE-588b)5008462-8$$6P:(DE-Juel1)143606$$aForschungszentrum Jülich$$b0$$kFZJ
001024153 9101_ $$0I:(DE-588b)5008462-8$$6P:(DE-Juel1)174136$$aForschungszentrum Jülich$$b1$$kFZJ
001024153 9101_ $$0I:(DE-588b)5008462-8$$6P:(DE-Juel1)132268$$aForschungszentrum Jülich$$b2$$kFZJ
001024153 9131_ $$0G:(DE-HGF)POF4-511$$1G:(DE-HGF)POF4-510$$2G:(DE-HGF)POF4-500$$3G:(DE-HGF)POF4$$4G:(DE-HGF)POF$$9G:(DE-HGF)POF4-5112$$aDE-HGF$$bKey Technologies$$lEngineering Digital Futures – Supercomputing, Data Management and Information Security for Knowledge and Action$$vEnabling Computational- & Data-Intensive Science and Engineering$$x0
001024153 9141_ $$y2024
001024153 915__ $$0StatID:(DE-HGF)0510$$2StatID$$aOpenAccess
001024153 920__ $$lyes
001024153 9201_ $$0I:(DE-Juel1)JSC-20090406$$kJSC$$lJülich Supercomputing Center$$x0
001024153 980__ $$aconf
001024153 980__ $$aVDB
001024153 980__ $$aI:(DE-Juel1)JSC-20090406
001024153 980__ $$aUNRESTRICTED
001024153 9801_ $$aFullTexts