Hi,
> * Spectre mitigations? (I would think not, unless redhat has
> backported to gcc 4.8)
[1] mentions GCC upgrades along with retpoline-based mitigation (these
upgrades apparently came with RHEL 6.10).
> * Compare executable text size. (use 'size' not 'ls')
>
>> ... OS-independent thread pool ...
Good thoughts. Here's another idea:
* Excessive cache misses due to a slight increase in size of some
heavily used data structure? You could try firing up the profiler to get
some statistics:
$ perf stat -d ./application
Martin
[1] https://www.redhat.com/archives/rhelv6-announce/2018-June/msg00000.html
--
Martin Konrad
Facility for Rare Isotope Beams
Michigan State University
640 South Shaw Lane
East Lansing, MI 48824-1321, USA
Tel. 517-908-7253
Email: konrad at frib.msu.edu
- Replies:
- RE: EPICS shared library performance Mark Rivers via Core-talk
- References:
- EPICS shared library performance Mark Rivers via Core-talk
- Navigate by Date:
- Prev:
Re: EPICS shared library performance Michael Davidsaver via Core-talk
- Next:
Build failed: EPICS Base 7 base-7.0-41 AppVeyor via Core-talk
- 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: EPICS shared library performance Michael Davidsaver via Core-talk
- Next:
RE: EPICS shared library performance Mark Rivers via Core-talk
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
<2020>
2021
2022
2023
2024
|