Experimental Physics and Industrial Control System
Hi all,
I am jumping in the middle of the discussion throwing in some ideas:
- Current CPU's provide more memory than 'typically' needed for our
applications. This will even improve in the future.
So why not really leave the malloc to the OS?
We could still support a macro replacement to stay compatible with old
(small memory footprint) systems using the 'EPICS' malloc.
- Default monitoring of the memory size and the fragmentation could at
least be used for alarms.
- High water marks for fragmentation could be used to 'protect' the most
important applications against misbehaved applications (obviously not
EPICS!) which might reside on the IOC. I.e. a Java VM could 'steal' a
lot of memory and cause fragmentation on the IOC. We could define
'rules' for non-EPICS applications to follow.
Sorry if this is nothing new in this discussion...
-Matthias
- References:
- again: memory management Benjamin Franksen
- Re: again: memory management Kay-Uwe Kasemir
- Navigate by Date:
- Prev:
Re: again: memory management Kay-Uwe Kasemir
- Next:
Re: Record support and user-defined fields Kay-Uwe Kasemir
- Index:
2002
2003
2004
<2005>
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Re: again: memory management Kay-Uwe Kasemir
- Next:
Re: again: memory management Benjamin Franksen
- Index:
2002
2003
2004
<2005>
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024