aboutsummaryrefslogtreecommitdiffstats
path: root/lib/compiler/test/inline_SUITE_data
diff options
context:
space:
mode:
authorUlf Wiger <[email protected]>2010-05-09 12:15:56 +0200
committerUlf Wiger <[email protected]>2010-05-09 12:15:56 +0200
commit82c090488eb76d16e8b828bb8f050afd0949e4c4 (patch)
tree6332210528c3bc10ad60fb526f415c1b7055e8a5 /lib/compiler/test/inline_SUITE_data
parenta21a9dac550bcb976fa074d7005499a4d6b55791 (diff)
downloadotp-82c090488eb76d16e8b828bb8f050afd0949e4c4.tar.gz
otp-82c090488eb76d16e8b828bb8f050afd0949e4c4.tar.bz2
otp-82c090488eb76d16e8b828bb8f050afd0949e4c4.zip
Enable continuous monitoring of mnesia overload status
Mnesia currently issues an event whenever it detects an overload condition. It recognizes two different types of overload: - whenever the message queue of mnesia_tm process grows large - when a log dump interval triggers before the previous dump is done These events could be used to trigger a load regulation mechanism to reduce the load until the condition seizes. The missing piece is that there is no facility to ask mnesia whether the overload condition still exists. This patch implements a couple of functions in mnesia_lib that can be used to sample the overload status. It has been tested in a load regulator component being developed by Erlang Solutions. No mnesia test suites have been run, since they are not available. No documentation has been updated. The functions in mnesia_lib are at any rate undocumented (as are all other functions in that module). A decision would have to be made about whether to provide a documented API on top of these functions. The internal state record of mnesia_recover has been modified. For this reason, a code change hook has been provided.
Diffstat (limited to 'lib/compiler/test/inline_SUITE_data')
0 files changed, 0 insertions, 0 deletions