|
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: 2487
Entry time: 28 Apr 2023
In reply to: 2486
|
Author: |
Marius Koeppel |
Topic: |
Suggestion |
Subject: |
Maximum ODB size |
|
|
> At the run start mlogger writes the ODB to the .mid file. This needs conversion (binary ODB -> XML ASCII) which can take time.
> This does NOT depend on the ODB size, but on the ODB *content*. Every key in the ODB takes time to convert. So if your ODB as 1.5 GB
> but only a few keys, this is still fast. Only if you have 200 million keys int he ODB, then mlogger takes lots of time to convert
> 200 million values to XML or JSON strings.
This was also my assumption. Is this the same for odbedit -c save FILE?
Because this is what I tested with the script and there one can see in the plot that the time increases to write the file if the ODB size increases.
The content of the ODB is always the same - one STRING key in the directory Test.
Best,
Marius |