|
|
|
Back
Midas
Rome
Roody
Rootana
|
| Midas DAQ System |
Not logged in |
 |
|
23 Apr 2026, Pavel Murat, Bug Report, increasing the max number of hot links in ODB
|
24 Apr 2026, Konstantin Olchanski, Bug Report, increasing the max number of hot links in ODB
|
25 Apr 2026, Pavel Murat, Bug Report, increasing the max number of hot links in ODB
|
27 Apr 2026, Konstantin Olchanski, Bug Report, increasing the max number of hot links in ODB
|
26 Apr 2026, Stefan Ritt, Bug Report, increasing the max number of hot links in ODB
|
27 Apr 2026, Konstantin Olchanski, Bug Report, increasing the max number of hot links in ODB
|
27 Apr 2026, Nick Hastings, Bug Report, increasing the max number of hot links in ODB
|
27 Apr 2026, Pavel Murat, Bug Report, increasing the max number of hot links in ODB
|
27 Apr 2026, Pavel Murat, Bug Report, increasing the max number of hot links in ODB
|
|
|
Message ID: 3216
Entry time: 27 Apr 2026
In reply to: 3214
Reply to this: 3217
3219
|
| Author: |
Konstantin Olchanski |
| Topic: |
Bug Report |
| Subject: |
increasing the max number of hot links in ODB |
|
|
> I wonder why one needs more than 256 hotlinks at all.
I confirm that ALPHA is running with MAX_OPEN_RECORDS changed from 256 to 2048,
this is the only experiment I know of that had to increase any MIDAS ODB defaults.
The reason for this is mlogger, it opens an open record for each variable in each equipment.
This should be changed to 1 db_watch per equipment. We talked about it, but I guess we never did it.
I think this task just went almost to the top of my MIDAS to-do list.
K.O. |