|
Back
Midas
Rome
Roody
Rootana
|
Midas DAQ System |
Not logged in |
|
|
31 Mar 2022, Stefan Ritt, Suggestion, Maximum ODB size
|
04 Apr 2022, Konstantin Olchanski, Suggestion, Maximum ODB size
|
27 Apr 2023, Marius Koeppel, Suggestion, Maximum ODB size
|
27 Apr 2023, Konstantin Olchanski, Suggestion, Maximum ODB size
|
27 Apr 2023, Marius Koeppel, Suggestion, Maximum ODB size
|
27 Apr 2023, Konstantin Olchanski, Suggestion, Maximum ODB size
|
27 Apr 2023, Konstantin Olchanski, Suggestion, Maximum ODB size
|
28 Apr 2023, Marius Koeppel, Suggestion, Maximum ODB size
|
28 Apr 2023, Stefan Ritt, Suggestion, Maximum ODB size
|
28 Apr 2023, Marius Koeppel, Suggestion, Maximum ODB size
|
28 Apr 2023, Konstantin Olchanski, Suggestion, Maximum ODB size
|
27 Apr 2023, Stefan Ritt, Suggestion, Maximum ODB size
|
28 Apr 2023, Konstantin Olchanski, Suggestion, Maximum ODB size
|
09 Jun 2023, Konstantin Olchanski, Suggestion, Maximum ODB size
|
12 Jun 2023, Stefan Ritt, Suggestion, Maximum ODB size
|
12 Jun 2023, Konstantin Olchanski, Suggestion, Maximum ODB size
|
13 Jun 2023, Stefan Ritt, Suggestion, Maximum ODB size
|
13 Jun 2023, Marius Koeppel, Suggestion, Maximum ODB size
|
13 Jun 2023, Konstantin Olchanski, Suggestion, Maximum ODB size
|
13 Jun 2023, Konstantin Olchanski, Suggestion, Maximum ODB size
|
13 Jun 2023, Stefan Ritt, Suggestion, Maximum ODB size
|
13 Jun 2023, Konstantin Olchanski, Suggestion, Maximum ODB size
|
13 Jun 2023, Stefan Ritt, Suggestion, Maximum ODB size
|
15 Jun 2023, Konstantin Olchanski, Suggestion, Maximum ODB size
|
28 Jul 2023, Stefan Ritt, Suggestion, Maximum ODB size
|
09 Aug 2023, Konstantin Olchanski, Suggestion, Maximum ODB size
|
|
Message ID: 2483
Entry time: 27 Apr 2023
In reply to: 2477
Reply to this: 2488
|
Author: |
Stefan Ritt |
Topic: |
Suggestion |
Subject: |
Maximum ODB size |
|
|
> Congratulations. created != "it works".
Two other tings to consider:
1) The ODB shared memory is dumped into a binary file (".ODB.SHM") after the last client finished and read if the first client starts, to get it persistent.
So this could slow down starting and stopping, but only the first client, so I guess it's not an issue.
2) Traditionally, the ODB gets dumped to the .mid file at the beginning and end of every run, so that one know the exact configuration of the experiment
for offline analysis. This can be turned off of course, but most experiments use it. If the ODB is dumped in any ASCII format, this can take quite long.
Assume it takes 10 seconds at the beginning of each run, and we take a run every five minutes. Then we loose 48 mins of precious beam time every day.
Best,
Stefan |