Skip to content
Snippets Groups Projects

Remove rob set caching from DataProviderTools

Merged Adam Edward Barton requested to merge abarton/athena:ProviderToolCacheRemoval into master
1 unresolved thread

I remove the rob sets that prevent repeat decoding from the DataProvidersTools, in the trigger 'views' system we want to use identifiableContainer caches to avoid repeat decoding based on the per hash level. Currently we are seeing inconsistent results and believe the rob set caching is causing conflict.

@oda @goetz @stsuno @sutt @zgrout Can we remove this rob set check? Do you foresee any problems in other areas?

Edited by Adam Edward Barton

Merge request reports

Loading
Loading

Activity

Filter activity
  • Approvals
  • Assignees & reviewers
  • Comments (from bots)
  • Comments (from users)
  • Commits & branches
  • Edits
  • Labels
  • Lock status
  • Mentions
  • Merge request status
  • Tracking
109 #endif
110 } else {
111 StatusCode sc = m_decoder->fillCollection(&**rob_it, rdoCont);
112 if (sc != StatusCode::SUCCESS) {
113 if (DecodeErrCount < 100) {
96 StatusCode sc = m_decoder->fillCollection(&**rob_it, rdoCont);
97 if (sc != StatusCode::SUCCESS) {
98 if (m_DecodeErrCount < 100) {
114 99 if (msgLvl(MSG::INFO)) msg(MSG::INFO) << "Problem with BCM ByteStream Decoding!" << endmsg;
115 } else if (100 == DecodeErrCount) {
100 } else if (100 == m_DecodeErrCount) {
116 101 if (msgLvl(MSG::INFO)) msg(MSG::INFO) << "Too many Problems with BCM Decoding. Turning message off." << endmsg;
117 }
118 DecodeErrCount++;
102 }
103 m_DecodeErrCount++;
  • If m_DecodeErrCount becomes atomic and depending on the error frequency it might be better to first increment a local counter and add the local counter to m_DecodeErrCount outside the loop.

  • Please register or sign in to reply
Please register or sign in to reply
Loading